PWS_for_RFI_2024.docx (1).pdf

DR

AF

T

PERFORMANCEWORK STATEMENT (PWS)

FOR

TEAMCENTER PROFESSIONAL

ENGINEERING SERVICES SUPPORTING

MODERNIZATION AND PLM PROGRAMS

T

Table of Contents

1. INTRODUCTION

1.1. Purpose

1.2. Scope

1.3. Background

2. REFERENCE DOCUMENTS

2.1. Military Standards

2.2. USAF Documents

3. CONTRACTOR TASKING

3.1. Task Requirements

3.2. Skill Levels

3.2.1. Skill/Knowledge Maintenance and Augmentation

3.3. Positions and Hours

3.4. Software

3.4.1. Software Usage Support

3.5. Hardware

4.1. Period of Performance

4.2. Delivery Schedule

5. PROGRAMMANAGEMENT

5.1. Program Management

5.1.1. Single Manager

5.1.2. Monthly Status Report (MSR)

5.1.3. Financial Tracking

5.1.4. Metrics

5.1.5. Meetings

6. SPECIAL CONSIDERATIONS

6.1. Security

6.1.1. Data Usage

6.1.2. Clearance

6.1.3. Forms Processing

6.1.4. System Access and Protection

6.2. Access to Government Facilities and Property

6.2.3. ID/Common Access Card (CAC)

6.3. Government Furnished Equipment, Materials, and Software

6.4. Government Provided Office Space

6.5. Government Program and Contract Management

6.5.1. Government Program Management

6.5.2. Government Contract Management

6.5.3. Contractor Manpower Reporting

6.6. General Safety Requirements

7. TRAVEL REQUIREMENTS

8. SERVICE SUMMARY

9. APPENDICES

9.1. APPENDIX A - Acronyms and Abbreviations

T

9.2. APPENDIX B - Safety

9.3. APPENDIX C – Travel Request Form

1. INTRODUCTION

The Air Force has prioritized a transformation of its operations and data from paper documents and corresponding individual flat file data repositories to digital data, including digital twin concepts with integrated including digital twin concepts. To this end, the Air Force has implemented Siemen’s Teamcenter Product Lifecycle Management (PLM) to control lifecycle change requirements for the weapons system. Individual AF Program Offices (PO) are implementing Teamcenter PLM to meet their needs. The need for PLM implementation engineering services is expanding within the AF. This PWS will accomplish Engineering services to assist AF Program Offices to implement Siemens Teamcenter PLM at their various locations for their specific needs. The contractor shall have the ability to provide the full range of Teamcenter support services needed to successfully implement Teamcenter PLM at the various AF Program Offices. Task Orders will be scaled to meet individual requirements, but it is expected that the contractor shall have the resources and experience to meet all possible Teamcenter PLM support requirements as described in the scope section below.

1.1. Purpose

The purpose of this effort is for the contractor to provide non-personal technical support services to include all management, labor, materials, and necessary Teamcenter Professional Services to satisfy the Air Force PLM environment across multiple locations within the Air Force.

1.2. Scope

The technical support services required for this effort include Teamcenter Professional Engineering Services to support the Air Force PO Engineering staff implementing their PLM requirements. Highly skilled, experienced Teamcenter engineering services are paramount to application administration, business process modeling, PLM functionality/module configuration. This effort requires working in a leading-edge Computer -aided Design (CAD) environment with a mix of 2D and 3D data; some with drawings and some without. All of the engineering data created exists in CAD models and a Teamcenter database.

The contractor shall provide Teamcenter PLM engineering services that support the various program office lifecycle transition efforts utilizing PLM, including, but not limited to business processes and data associated with: Acquisition Support, Sustainment Support, Spare Part buys, Provisioning, Overhauls, Packaging, Maintenance Execution, etc.

Teamcenter PLM examples that these services will be supporting include, but not limited to the following tasks:

1) Teamcenter Installation Support

a. Local Data Center Support

b. Cloud Implementation

c. Cloud Migration

T

d. Load balancer

e. AWC server configuration support

f. Teamcenter Service Management Application (TSMA)

g. Interface to other AF/DoD systems

2) Teamcenter Administration Support

a. BMIDE Changes

b. Data Exchange Standards

c. CAD Integration

d. Teamcenter Dispatcher utilities

e. Interface and coordinate with hosting data service providers

f. Teamcenter configuration management support (BMIDE)

g. Data import and export

h. Data clean up routines

i. Teamcenter User accounts, Help Desk, Training, Organization Change

Management (OCM) Support

j. Teamcenter Change Management Support

i. Version upgrades

k. Teamcenter Reporting and Analytics

l. Teamcenter User Interfaces (RAC and AWC)

m. Aerospace and Defense Template

3) Teamcenter Application Module Support

a. Change Management

b. Contract Data Management

c. Service Engineering

d. Requirements Management

e. Document and Content Management

f. Sim Manager

g. Manufacturing Planning/Tecnomatics

h. Classification

i. Supplier/Vendor Management

j. Integrated Material Management

4) USAF Teamcenter Functionality Development

a. Teamcenter Business Process Management mapping and Implementation

5) Interface with other AF and DoD systems

a. Provisioning

b. Present AF/DoD Maintenance Execution Systems

i. REMIS, IMDS, Imprezza

c. Other AF Digital Engineering initiatives

i. MRO

ii. ESCAPE

iii. FLTS

d. Defense Logistics Agency

e. Packaging groups

f. ETIMS (Technical Manuals)

g. JEDMICS (Drawing Repository)

h. Organic Program Office databases

T

i. Various present sustainment systems

j. Other AF/DoD PLM Systems

k. Requirements tracking systems

These examples are not comprehensive. These are examples of scope that the contractor support personnel will be asked to support. The full capabilities needed will be specified at the Task Order level.

1.3. Background

Multiple AF Program Offices are in various stages of transitioning to digital data. Many have implemented Siemen’s Teamcenter PLM to facilitate this digital transformation and manage their weapon systems. Additionally, the Assistant Secretary of the Air Force for Acquisition, Technology, & Logistics has deemed this Commercial off the Shelf (COTS) tool the USAF PLM the system of choice for all programs moving forward. Presently, the digital engineering concepts and data have focused on 3D Model Based Definition (MBD), in support of modernized weapon systems. Because of the capabilities inherent in the Teamcenter PLM tool, these programs are moving to transition their document-based data to digital data. They are automating manual business processes utilizing Teamcenter PLM workflows. They also require integration of data, control of data and data ownership, integration with other systems, and visualization of this data in PLM. The ultimate goals for the AF and DoD are to be able to utilize the data they presently have, but also be able to host the digital twin concept in a weapon system PLM system. Since these capabilities are relatively new to the AF, the PLM digital engineering services provided must be highly competent and utilize experienced Teamcenter PLM personnel to meet the AF PLM digital transformations in a timely manner.

Previously AF programs had to utilize individual PLM engineering service support contracts from multiple vendors. This has resulted in disparate system architectures and approaches.

Utilizing a single support contractor, the AF hopes that similar capabilities and functionality can be readily communicated and shared across program offices that utilize the engineering services provided on this PWS.

2. REFERENCE DOCUMENTS

The documents listed below govern the creation, validation, relationships, and import/export of data as well as the workflow processes for change control within the PLM environment.

Contractor is responsible for compliance to referenced documents and any updates occurring within these documents through the life of the contract.

2.1. Military Standards

A. MIL-HDBK-61A, Configuration Control B. MIL-STD-1530D, Aircraft Structural Integrity Program, Airplane Requirements, Sections 1-5.

C. MIL-STD-38784, Standard Practice for Technical Manuals; General Style and Format

Requirements D. MIL-I-8500, Military Specification: Interchangeability and Replaceability of

Component Parts for Aerospace Vehicles

T

2.2. USAF Documents

A. AFI 63-101/20-101 Integrated Lifecycle Mgmt B. AFPD 63-1/20-1 Integrated Lifecycle Management C. AFPAM 63-128 Integrated Lifecycle Management D. AFMCI 63-1201 Implementing OSS&E and Life Cycle Systems Engrg E. AFI 63-133 Acft Information Program F. AFMAN 63-1202_ETAR Process G. Air Force Instruction (AFI) 21-402, Engineering Drawing System H. AFI 31-101, Volume 1, The Air Force Installation Security Program I. AFI 31-501, Personnel Security Program Management

3. CONTRACTOR TASKING

The Contractor shall provide Teamcenter Professional Services to support the PLM requirements in the following areas: the production and sustainment of the Technical Data Package (TDP), system-to-system interfaces, data migrations, and development of Teamcenter administration skills for personnel. The contractor shall configure the Teamcenter PLM system and related Teamcenter processes, data, forms and artifacts to implement these tasks. This requirement requires extensive face-to-face communication with on-site government and contractor personnel to work ongoing issues. Working these issues will often require side-by-side, hands-on interaction at a workstation to determine if the proposed technical solutions are meeting requirements. This interaction is expected to occur frequently, essentially on a daily basis. Therefore, the government has determined this requirement must be met by providing personnel available on-site during normal business hours throughout the period of performance for the Primary Positions and, at a minimum, one week per month for the Secondary Positions (these may work remotely for the other weeks of the month).

Place of Performance: A majority of the work will be performed at the AF Product Centers to include Hill Air Force Base (AFB), Ogden UT, Wright Patterson, AFB, OH; Warner Robins AFB, GA, and potentially any other AFB.. The actual sites will be defined by the specific Task Order.

3.1. Task Requirements

To ensure the successful implementation and support of Teamcenter, the contractor shall:

a) Identify and maintain the best Configuration Item (CI) management approach necessary to manage the MBD approach along with the legacy 2D drawing approach.

b) Manage the creation and loading processes of new data, drawing numbers, and Engineering Order (EO) numbers mapped to workflow processes in Teamcenter.

c) Author/Update/Consult on Operating Instructions (OI) to manage, sustain, and modify the configuration management approach for the TDP.

d) Provide hosting service (Cloud or datacenter) with application administration to set up the necessary IT infrastructure (Teamcenter & Oracle databases) to manage, T sustain, and modify the configuration management approach defined for the TDP and its down-stream uses.

e) Provide hosting service (Cloud or datacenter) oversight for the Teamcenter environment within the government firewall to ensure it functions properly, maintains synchronization with contractors outside the firewall, and allows depot and field support personnel to connect to and use the TDP.

f) Provide hosting service (Cloud or datacenter) computer support for diagnosis and correction of software installs that negatively affect Teamcenter operation at the desktop; to include Author/Update/Consult on Teamcenter/NX/JT2Go installation scripts, error log review/debug, login issues, and physical edits to the computer as allowed by administrative rights.

g) Develop additional government workflows to manage change of 3-D and 2-D engineering data, TOs, TCTO, Specifications, etc.

h) Maintain developed interfaces between Teamcenter and the government engineering data management systems (i.e., Weapon System Management Tool (WSMT) and Reliability & Maintainability Information System (REMIS)), to ensure configuration control and synchronization of the Program Office TDP.

i) Develop and maintain processes for notifying the government and downstream users of changes to the TDP.

j) Author/Update/Consult on OIs and PLM Data Exchange Specification (ADES) procedures concerning the validation of data, data importing, and data synchronization to ensure the accuracy and completeness of the TDP.

k) Author/Update/Consult on procedures, part reports, and simplified drawings using PO CAD system and Teamcenter as related to structural, mechanical, electrical, and hydraulic systems.

l) Author/Update/Consult on procedures for personnel to use, support and modify the CAD data created under the various contracts.

m) Author/Update/Consult on procedures to transition, validate, and sustain the TDP created. The effort shall support both incremental and end-of- contract validations.

n) Develop, support and maintain Maintenance Manual (Technical Orders) related to the engineering data as well as the serialized units it is applicable to.

o) Develop data models, workflows to transition TOs from SGML sourced data to S1000D content using the Teamcenter Content Management module.

p) Develop TC data models, workflows, forms, GUI refinements (based on user role) and relationships to other data to manage the maintenance requirements of the appropriate fleet, including individual serialized units, using the Teamcenter Service Data module.

q) Develop TC data models, workflows, forms, GUI refinements (based on user role) and relationships to other data to manage the contract requirements of the System Program Office for data acquired and managed within the PO Teamcenter PLM database or specified within awarded Task Order.

T

r) Conduct lean events, user training, and application demonstrations in support of streamlining existing processes into more structured workflows for consistency, accuracy, and control of engineering data.

s) Provide and present training materials for Teamcenter administration personnel that will meet the Siemens Teamcenter Administrator certification (Expert Series) requirements. Since AF computers and network may not allow the required training software or computer Admin Rights, the contractor shall provide the off-site location as well as computers for any personnel who cannot use their own personal computer.

t) Develop new, or update existing, functional specifications, design specification and test scripts necessary to meet policy and/or user requirements using established templates.

u) Develop datacenter to AF Cloud migration strategies for schema changes, data migration, system administration oversight, and application administration performance.

v) Conduct weekly Technical Interchange Meetings (TIM) to gauge PLM implementation progress and status for all stakeholders. Provide meeting agenda and minutes (to be conducted at the task order level and provided at the task order level)

w) Provide monthly status updates to AF on work performed. (to be conducted at the task order level and provided at the task order level)

3.2. Skill Levels

The Government has determined that performing these services are at a Teamcenter enterprise level. The contractor shall be responsible for providing an organizational team structure possessing the knowledge, skills, and experience capable of performing Teamcenter support and services, which includes knowledge, skills and experience of a Senior Teamcenter Solutions Architect and multiple Senior Teamcenter Implementation Engineers/Consultants. The following skills, knowledge, and experience are required (note, additional consultants do not require ‘specialist’ skill set levels):

TABLE 1: Minimum Personnel Qualifications

POSITION EDUCATION CLEARANCE &

EXPERIENCE

Skills

Senior Teamcenter Solutions Architect

At least a Bachelor of Science in Engineering, Computer Science, or Information Management, or degree with related experience.

Clearance:

Must possess the eligibility equal to or greater than an

ANACI/T3/NACLA

background investigation or Secret Clearance

Experience:

Senior Teamcenter Solutions Architect, 10 years of experience

a) An expert at developing interfaces and workflows in Teamcenter for managing engineering data.

b) Proficient in configuration management of parts, assemblies, and installation of aircraft engineering data.

c) Proficient with using Teamcenter to create/manage engineering data and engineering related workflows.

d) Proficient in architecting, implementing, programming, and

T managing database schemas in Teamcenter.

e) Knowledgeable and proficient in creating and managing engineering change processes within Teamcenter.

f) Experienced in using Oracle databases to manage engineering data. Experienced with programming interfaces and collaborating data contained in Oracle based database systems with data contained in Teamcenter databases for migration and management of engineering data.

g) Proficient in monitoring process logs, improvements needed, and implementing changes to the Teamcenter application configuration to enhance and improve operations.

h) Proficient in developing block diagrams and logic flow charts and developing data and security models.

i) Knowledgeable in preparing documentation of system configuration (i.e., DODAF Architecture) and user documentation.

j) Proficient in preparing test, debugging and validation plans for PLM implementation and upgrades.

k) Proficient in mapping/migrating existing PO Teamcenter schema to AF Cloud One and Platform One instances of Teamcenter.

l) Must possess and maintain MS Security Plus certification required for administrative access to AF computers.

Senior Teamcenter Implementation Engineer/Consultan t

At least a Bachelor of Science in Engineering, Computer Science, or Information Management, or degree with related experience.

Clearance:

Must possess the eligibility equal to or greater than an

ANACI/T3/NACLA

background investigation or Secret Clearance

Experience:

Full-Time Senior Teamcenter Implementation

a) An expert at developing interfaces and workflows in Teamcenter for managing engineering data.

b) Proficient in configuration management of parts, assemblies, and installation of aircraft engineering data.

c) Proficient with using Teamcenter to create/manage engineering data and engineering related workflows.

T

Engineer/Consultant – 5 years of experience

d) Knowledgeable and proficient in creating and managing engineering change processes within Teamcenter.

e) Experienced in using Oracle databases to manage engineering data. Experienced with programming interfaces and collaborating data contained in Oracle based database systems with data contained in Teamcenter databases for migration and management of engineering data.

f) Proficient in monitoring process logs, improvements needed, and implementing changes to the Teamcenter application configuration to enhance and improve operations.

g) Proficient in developing block diagrams and logic flow charts and developing data and security models.

h) Proficient in preparing test, debugging and validation plans for PLM implementation and upgrades.

i) Proficient in mapping/migrating existing PO Teamcenter schema to AF Cloud One and Platform One instances of Teamcenter.

j) Must possess and maintain MS Security Plus certification required for administrative access to AF computers.

The following definitions shall be applied to the skill levels above:

Expert: You are known as an expert in this area. You can provide guidance, troubleshoot and answer questions related to this area of expertise and the field where the skills are used. You understand not only how to perform the task or operation but understand the reasons and interrelationships to other elements affecting the outcome.

Proficient: You can perform the actions associated with this skill without assistance. You are certainly recognized within your immediate organization as “a person to ask” when difficult questions arise regarding this skill or task due to your skill and efficiency.

Knowledgeable: Knows at a working level how to implement the task at hand based upon extensive previous experience (e.g., multiple times performing the same or very similar tasks), such that reference or refreshing of knowledge is not required.

T

3.2.1. Skill/Knowledge Maintenance and Augmentation

The contractor shall be knowledgeable of all changes to software versions of Teamcenter and NX as well as the transition process when new Teamcenter releases are available. The contractor shall ensure all personnel are trained and current on the latest software updates/capabilities and industry standard best practices to meet the Government’s Teamcenter needs. To help meet the needs in this section, the contractor shall also ensure each Primary and Secondary personnel attend the annual Siemens Realize Live event. Travel for attendance shall be approved by the government Program Manager. See paragraph 7 for additional travel requirements.

3.3. Software

The contractor shall provide government-use licenses and annual maintenance of the software listed below for the administration of the Teamcenter/CAD environment to be performed at the government facilities. The software versions shall be compatible with the government’s current systems for type, operating systems, and approvals for loading on the AF network.

The software shall be license-based and shall be loaded, accessed and maintained accordingly on the hardware provided by this effort (section 3.5) and/or the government’s server consistent with present site licensing using the FLEXLM License manager***. The contractor shall provide for annual maintenance of this software during the duration of this contract along with upgrades required to meet the Teamcenter/CAD revision updates.

Existing Software Requiring Annual Maintenance and latest version upgrades

Assigned to stand-alone development laptops:

Microsoft Open License Agreement: MOLP-Z Local Government MS Windows 10 MS Office Professional 2016 MS Visio 2016 MS Visual Studio Professional MS Team Foundation Server 2018 License with Eclipse plugin (https://www.visualstudio.com/team-services/tfs-pricing/)

MS Team Foundation Server Client Access License (https://www.visualstudio.com/team-services/tfs-pricing/)

(1) MS Windows Server License (check with the Air Force Program Office for version before purchase)

Assigned to contractor purchased/used laptops:

Siemens Teamcenter* ** Siemens Vis Mockup* **

New Software to Be Purchased

Assigned to stand-alone development laptops:

McAfee Anti-Virus protection https://www.visualstudio.com/team-services/tfs-pricing/ https://www.visualstudio.com/team-services/tfs-pricing/

T

*** Servers that support these license will be defined by the Program Office in the specific Task Order.

3.3.1. Software Usage Support

The contractor shall provide software usage support as necessary for the PO PLM support personnel to properly use and apply the software for the creation, modification, review and storing of the data created or supported under this effort. This includes, but is not limited to, user desktop instructions, lunch-n-learn demonstrations, identifying self-paced learning/reviewing media, etc.

3.4. Hardware

The contractor shall provide one engineering grade laptop per Primary and Secondary (if applicable) positions at the Task Order Level, or as outlined in Paragraph 3.3, and certified to run any 3D CAD defined by the program office at the Task Order, Teamcenter 13, and AWC

5.1 or better. The laptops shall be a Windows 10 Professional based operating system with sufficient capacity (processing power, RAM, hard drive storage capacity, video graphics controllers, monitors and input devices) to perform PLM data import and exporting, CAD modeling and handle large CAD assemblies for PLM CAD visualization support. The systems shall be consistent with new or existing engineering laptop configurations needed to support the specific tasks order. The contractor shall purchase maintenance agreements for provided hardware for the duration of this effort (including option years of contract). All hardware and software versions shall be validated with the appropriate program office before being purchased. Hardware requirements will be identified within each TO.

The current standard for an engineering laptop is:

Dell Precision 7750

Description: QEB 2021A MOBILE WORKSTATION 17.0 – DELL PRECISION 7750: INTEL I7-10750H, 2.6/5.0GHZ, 17.3 FHD W/LED BACKLIGHT, 32GB RAM, NVIDIA QUADRO T1000 W/ MINI DP, HDMI, (MINI DP TO DP ADAPTER), GIG NIC, 2 USB 3.2 TYPE A, 2 USB 3.2 TYPE C, IEEE 802.11AX WIRELESS, FIPS 201-2 INTERNAL CAC, 512GB SSD NVME, TPM 2.0 VERSION 1.38, WIN 10 OFFICE

SUITE 64-BIT- (SDC 5.X), 4-YR ON-SITE NBD WARRANTY W/HDD RETENTION.

Feature:

CARRY CASE: DELL PRO SLIM BRIEFCASE 15

OEM: DELL

OEM Part Number: 460-BCMK

PROCESSOR: INTEL CORE I7-10875H

OEM: DELL

OEM Part Number: 329-BEXD

DOCKING STATION: WD19DC DELL DOCK

OEM: DELL

OEM Part Number: 210-ARYR

HARD DRIVE: 1TB SSD NVME SED

OEM: DELL

T

OEM Part Number: 400-BEBS

KEYBOARD: DELL KB216 WIRED MULTI-MEDIA 104-KEY KEYBOARD ENGLISH, NO CAC READER

OEM: DELL

OEM Part Number: 580-ADJC

MOUSE: DELL MS116 WIRED 2-BUTTON OPTICAL MOUSE

OEM: DELL

OEM Part Number: 275-BBBW

OPERATING SYSTEM: NO UPGRADE

OEM: DELL

OEM Part Number: -

OPTICAL DRIVE: EXTERNAL BLU-RAY RW DUAL LAYER

OEM: DELL

OEM Part Number: A7441354

MEMORY: 128GB

OEM: DELL

OEM Part Number: 370-AFGQ

VIDEO CARD: NVIDIA RTX 3000

OEM: DELL

OEM Part Number: 490-BFUZ

External Monitors Quantity 2

QEB 2021A HIGH RESOLUTION DISPLAY UHD TRANSOURCE LG/27BL55U-B: 3840X2160, 27"

DIAGONAL (2) HDMI, AND (1) DISPLAYPORT; PIVOT, HEIGHT ADJUSTABLE, TILT ADJUSTABLE, EPEAT BRONZE, 3 YEAR ADVANCED REPLACEMENT/MAIL BACK.

To include a 3Dconnexion Space Navigator for notebooks for dynamic 3D rotation.

All hardware and software purchased as a part of this effort shall be considered Contractor Acquired Property (CAP) and shall become the possession of the government upon completion of this contract or anytime deemed necessary during this contract. As practicable, the contractor shall use DoD Supply Sources, such as AFWAY/Netcents to purchase this

CAP.

4. PERIOD OF PERFORMANCE AND DELIVERY SCHEDULE

4.1. Period of Performance

The base period of performance will be one year after the stated start date of the contract. There will be four, one-year options. Any TO placed before the end of the contract period may be performed during the period of performance stated in the TO provided that TOs that extend beyond the 4-year contract period must be completed within 12 months following the expiration of the basic contract ordering period

T

5. PROGRAMMANAGEMENT

The contract deliverables will be required pursuant to each TO and are ongoing under any active

TO.

5.1. Program Management

The Contractor shall provide software (IAW Paragraph 3.3) and hardware (IAW Paragraph 3.4 and all services required to efficiently and effectively manage this requirement. The Contractor shall establish and maintain a program management system tailored to accomplish the administrative, management, technical, and financial requirements of the tasks associated with this requirement.

5.1.1. Single Manager

The Contractor shall establish a single manager having authority and responsibility for the overall effort. The intent of the single manager is to give the Government a single point of contact to avoid possible duplication of effort from multiple tasks. Individual task managers reporting to the single manager may be designated by the Contractor. The Government single point of contact is the Government Program Manager (PM).

5.1.2. Monthly Status Report (MSR)

The Contractor shall provide a Monthly Status Report (MSR) for each awarded Task Order summarizing the actions that occurred during the time period. The MSR shall cover all program activities for the period and shall provide a forecast of work to be accomplished during the upcoming month. This report shall include activities performed in this contract.

The Contractor shall identify actions being taken to correct deficiencies. Changes from previous reports shall be highlighted and explained. The Contractor shall report any situation requiring immediate action by the Government using the most expedient means (teleconference, e-mail, or letter) and shall document the situation in the MSR. The MSR shall include the status of contract deliverables, including the preparation of engineering data.

5.1.3.Financial Tracking The Contractor shall provide summarized financial data in the MSR. The financial data shall summarize hours and funds expended for the month and totals for the period of the contract.

The financial data shall also itemize expenditures (actual billings) against obligations (contract line items).

5.1.4.Metrics The Contractor shall assist with travel and equipment inventory metrics required to support the USAF Government PM.

5.1.5.Meetings The Government encourages meetings with the Contractor to exchange information and ideas.

Although, whenever feasible, meetings shall be held in conjunction to minimize costs.

6. SPECIAL CONSIDERATIONS

T

6.1. Security

6.1.1.Data Usage Contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of Government systems. All requests for information shall be forwarded to the Government PM.

6.1.2.Clearance All contractors with access to Teamcenter on this contract must possess the eligibility equal to or greater than an ANACI/T3/NACLA background investigation or Secret Clearance within scope.

This requirement is for Information Systems level II access to the Teamcenter environment not classified information. Additionally, an ADP position category II (APD-II) shall be required for all personnel having access to the Teamcenter environment. Personnel assigned to this effort must possess these completed requirements at time of contract award and must maintain them for the duration of the contract.

6.1.3. Forms Processing

The USAF Government PM will assist Contractor personnel in processing the necessary DoD forms to obtain base or area badges for access to Government facilities.

6.1.4. System Access and Protection

The Contractor shall not divulge any information regarding files, data, processing activities/functions, user ID's, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all Government rules, procedures, and standard of conduct. Contractors requiring access to Government Automated Information Systems (AIS) shall have background investigations and security awareness training completed prior to the start of contract performance. When the period of performance is complete and/or Contractor personnel leave work on this project they shall have 5 days to terminate all their network user account and to return all access cards and base identification badges. Contractor personnel shall sign Non-Disclosure agreements prior to obtaining system access.

6.2. Access to Government Facilities and Property

Access to Government facilities is limited. Therefore, the Contractor shall coordinate the need, time and personnel requiring access with the Government PM at minimum, two weeks prior to need. The Government PM shall coordinate with applicable sites to assist Contractor personnel in processing the necessary information required for authorized access to designated units. If the site managers cannot meet the on-site visit requests of the Contractor, the Government PM, the Contractor, and the site managers will negotiate acceptable dates and times. All Contractor personnel shall comply with Program Office policies at the TO level: “Contractor Access to Base Facilities” and “Contractor Access to Air Force Automated Information Systems (AIS)”.

During performance of the task order, the Contractor shall be responsible for coordinating with the Government PM to obtain required identification for newly assigned personnel and to promptly return (NLT 5 working days) credentials for any employee who no longer requires access to the work site.

6.2.1. Hours of Operation.

T

On-site performance shall take place Monday-Friday between the core hours of 0600-1700.

Performance outside of these hours shall require prior approval from the Program Office.

Contractors are not authorized in Government facilities without a Government representative.

Vindicator cards for building access may be provided for contractor personnel.

6.2.2. Holidays and Energy/Family Days.

On-site performance shall not occur on the following observed Federal Holidays:

New Year’s Day - 1 January Martin Luther King Day - 3rd Monday in January Washington’s Birthday - 3rd Monday in February Memorial Day - last Monday in May Juneteenth – June 19 Independence Day - 4 July Labor Day - 1st Monday in September Columbus Day - 2nd Monday in October Veteran’s Day - 11 November Thanksgiving Day - 4th Thursday in November Christmas Day - 25 December

Note: If the holiday falls on a nonduty day, the holiday is normally observed the preceding or following duty day.

On-site performance shall not occur during Energy/Family Days (estimated 4 times per year) unless a Government representative is present during the core hours. Performance on these days shall be coordinated with the Program Office.

6.2.3. ID/Common Access Card (CAC)

For AF ID or CACs, if required, the Contractor shall submit a written request on company letterhead to the government Program Office at the TO level listing the following:

contract/task order number, location of work site, start and stop dates, and names of employees needing access to the base. The letter will also specify the individual(s) authorized to sign for a request for base identification credentials. When reporting to the registration office, the authorized Contractor individual(s) should provide a valid driver’s license, current vehicle registration, and valid vehicle insurance certificate. During performance of the task order, the Contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials for any employee who no longer requires access to the work site (NLT 5 working days).

Note, contractor personnel whose state issuing their driver license is non-compliant with the REAL ID Act of 2005 (Public Law 109-13,119STAT.302) and does not have an extension, will require a passport or other official pictured ID will be required for CAC processing.

6.3. Government Furnished Equipment, Materials, and Software

The Government will provide workspace, office furnishings, telephone service, computer resources, access to processors, terminals, printers, software, office supplies, data and communication networks, and other equipment necessary to complete the scope of work while on site. All products purchased under this task order shall be considered contractor acquired property and shall have no license encumbrances and shall be returned to the Government upon

T completion of this contract, unless the Contracting Officer decides a more efficient means of disposal.

6.4. Government Provided Office Space

The government will provide all needed office space for assigned contract personnel; full-time for Primary, and as required during on-site weeks for Secondary personnel.

6.5. Government Program and Contract Management

6.5.1. Government Program Management

The Government PM will provide the Contractor access to all technical data required to perform approved tasking. Only the USAF Government PM has authority to review and approve contract deliverables and are specified at the Task Order level.

6.5.2. Government Contract Management

Responsibility for contracting activities rests solely with the Government Contracting Officer.

No conversation, recommendations, or direction, whether given directly by, or implied by Government personnel, that will affect the scope, schedule, or price of the program covered by this PWS, shall be acted upon by the Contractor unless specifically approved by the Government Contracting Officer.

6.6. General Safety Requirements

The Contractor shall comply with all safety provisions, e.g., technical specifications, technical publications, Federal Occupational Safety and Health Standards (Title 29 CFR. Part 1910). If there is no applicable Occupational Safety and Health Administration (OSHA) standard, use other applicable nationally recognized sources of safety, health, and fire prevention standards referenced in the work requirements of this contract.

The Contractor shall protect Government property to prevent damage during the period of time the property is in the possession of the Contractor. The Contractor shall report promptly to the Contracting Officer (CO) all available facts relating to each instance of damage to Government property.

When a major mishap ($10,000 or more) involving Government property occurs, the Contractor shall immediately secure the accident scene and the damaged item until released by the accident investigative authority as designated by the Program Office at the task order level. Such release shall be accomplished by the CO.

If the Government elects to conduct an investigation of the accident, the Contractor shall cooperate fully and assist Government personnel until the investigation is completed.

The Contractor shall include a clause in each of its subcontracts requiring subcontractor cooperation and assistance in accident reporting and investigation.

See Appendix B for further safety requirements.

7. TRAVEL REQUIREMENTS

T

The Contractor shall travel in support of the above requirements and shall maintain the same level of service during the time of travel/trainings. Additional travel requirements will be identified in each Task Order.

Travel is estimated for: Secondary personnel (if applicable) to be on-site monthly at the designated AFB identified in the TO. Attendance at the Siemens Realize Live annual event, and travel to Air Force Program Supplier Facilities or other AF Bases to support PLM efforts.

(Example: Boeing; Northrop; Wright-Patterson AFB, OH; Warner Robbins, AFB, GA; etc.)

When travel is required, the contractor shall submit a Travel Request Form (see Appendix C) and submit the form to the USAF Government PM. The Contractor shall obtain approval from the Government PM at a minimum of 5 working days in advance of traveling;

approval shall be in writing/e-mail. Upon completion of any travel, the Contractor representative shall submit a trip report at the task order level. Airfare for travel and per diem shall be billed IAW Federal Travel Regulations (FTR) and FAR 31.205-46. The Contractor is responsible for making all necessary travel arrangements.

T

8. SERVICE SUMMARY/PERFORMANCE THRESHOLDS

Service Summary

Performance Objective

PWS

Para

Performance Threshold

1 Teamcenter Consulting Services

3.1 The contractor shall not have more than two instances of unsatisfactory work performance per submittal within this period. Any errors found will be provided to the contractor for correction within 10 working days.

2 Documentation and reports shall be developed IAW CDRLS defined at the Task Order level.

3.1 All actions accomplished as

required with no more than 2 disapprovals by the Government for technical discrepancies per technical/report. Any errors shall be corrected by the Contractor within 10 working days.

3 Deliveries shall be generated and delivered in a timely manner

3.1 Deliveries shall be timely;

delivered 9 out of 10 times on time. Provide a detailed get-well plan within 3 working days.

T

9. APPENDICES

9.1. APPENDIX A - Acronyms and Abbreviations

Acronym/Abbreviation Definition

AFI Air Force Instruction AFLCMC Air Force Life Cycle Management Center AFMC Air Force Materiel Command AIS Automated Information Systems CAD Computer-Aided Design CFR Code Federal Regulation CI Configuration Item CITOMS Comprehensive Integrated TO Management System CO Contracting Officer COTS Commercial Off the Shelf D220 Air Force Provisioning System DoD Department of Defense DOORS Dynamic Object-Oriented Requirements System -

IMB

Rational

EO Engineering Order ETIMS Enhanced Technical Information Management System EWA Enhanced Wing Assembly FAR Federal Acquisition Regulation FC/FD Functional Commander/Functional Director JEDMICS Joint Engineering Data Management Information

Control System MS Microsoft NAC National Agency Check NX Siemens (UNIGRAPHICS) CAD S/W OSHA Occupational Safety and Health Act PBSA Performance Based Service Acquisition PCO Procuring Contracting Officer QA Quality Assurance QAP Quality Assurance Personnel QASP Quality Assurance Surveillance Plan QC Quality Control PM Program Manager PO Program Office REMIS Reliability & Maintainability Information System SPO System Program Office S/N Serial Number SS Service Delivery Summary TC and Tc Teamcenter TDP Technical Data Package WSMT Weapon System Management Toolset

T

9.2. APPENDIX B - Safety

1. Environmental, Safety, And Occupational Health (ESOH): The contractor is solely responsible for compliance with all federal, state and local laws, the Occupational, Safety and Health Act (Public Law 91-596) and the resulting standards, OSHA Standards 29 CFR 1910 and 1926, as applicable, and the protection of their employees.

Additionally, the contractor is responsible for the safety and health of all subcontractor employees.

2. Voluntary Protection Programs (VPP): The Air Force is part of OSHA’s VPP. All contractors are required to familiarize themselves with the requirements of VPP.

Information on VPP can be accessed at http://www.osha.gov. The intent of the Air Force Safety Program is to prevent injuries and to communicate our safety expectations with potential offerors as well as those contractors awarded a government contract. The Air Force’s interest is to protect personnel working in or around contractor operations, and to protect Air Force equipment/property.

3. Contractor Employees: Compliance with OSHA and other applicable laws and regulations for the protection of contractor employees is exclusively the obligation of the contractor. Note: Air Force Occupational Safety and Health Standards (AFI’s) are annotated because many of the Air Force Standards exceed the OSHA standard criteria. If a conflict is noted, the most stringent requirement takes precedence. The government shall assume no liability or responsibility for the contractor's compliance or non- compliance with such requirements. The contractor shall furnish to each of his/her employees a place of employment, which is free from recognized hazards. The contractor shall brief his/her employees on the safety requirements of this contract and on hazards associated with prescribed tasks. The contractor is responsible for compliance with OSHA Public Law and the resultant standards identified within. In addition, the contractor is required to flow down the safety requirements/specification to all subcontractors. This applies to Federal Acquisition Regulation (FAR) Part 12 commercial acquisitions as well. This contract shall in no way require persons to work in surroundings or under working conditions which are unsafe or dangerous to their health. The contractor must coordinate and perform work so as not to impact the safety of government employees or cause damage to government property. This requires providing personnel with protective equipment and associated safety equipment as may be necessary. The contractor must also protect personnel from hazards generated by the work. If the contractor employs bilingual speaking employees, they must post bilingual signs and have written procedures for specific tasks in applicable languages.

4. Inspections: Air Force Environmental, Safety, Occupational Health and Fire protection officials or responsible Quality Assurance Evaluator (QAE) may periodically enter a contractor’s workplace to verify working conditions of Air Force personnel. If an Air Force employee observes improper procedures or unsafe conditions exits which place Air Force personnel or equipment/facilities in jeopardy, the contractor will remove personnel and/or equipment from the unsafe condition and immediately notify the Contracting Officer and the Installation Safety Office. Department of Labor (DoL), OSHA inspectors are authorized right of entry to inspect any place of employment operated by an Air Force contractor. They can be considered “no notice” inspections.

http://www.osha.gov/pls/oshaweb/owasrch.search_form?p_doc_type=STANDARDS&p_toc_level=0 http://www.osha.gov/pls/oshaweb/owasrch.search_form?p_doc_type=STANDARDS&p_toc_level=0 http://www.osha.gov/pls/oshaweb/owasrch.search_form?p_doc_type=STANDARDS&p_toc_level=0 http://www.osha.gov/

T

Noncompliance with safety requirements can result in work stoppage, inexcusable delays, and/or costly fines issued by the Department of Labor. The government shall assume no liability or responsibility for the contractor's compliance or non-compliance with such requirements. Fines and additional costs for violations levied against the contractor as a result of OSHA findings, and/or installation safety, fire, health or environmental are the sole responsibility of the contractor and shall not be passed through to the Government.

5. Mishap Notification: The contractor shall notify the AFLCMC Safety Office telephonically at (937) 904-3386 during duty hours and (937) 510-1184 after hours. Also notify the contracting units safety office at (801) 777-3333 during duty hours and (801) 777-3007 after hours, within four (4) hours after initial notification of all mishaps or incidents for damage to DoD property (material plus labor) entrusted by this contract and employee injuries as a result of the contract operation. A follow-up (written or e-mail) of this mishap/incident notification shall be sent within three calendar days to the Government Representative, the Procurement Contracting Officer (PCO) or the Administrative Contracting Officer (ACO) (with a copy to the government PM), who will forward it to the Installation Safety Office. The information that is not available at the time of the initial notification shall be provided within 20 calendar days after the mishap. Mishap notification shall contain, as a minimum, the following information:

a. Contract, Contract Number, Name and Title of Person(s) Reporting

b. Date, Time and exact location of accident/incident

c. Brief Narrative of accident/incident (Events leading to accident/incident)

d. Cause of accident/incident, if known

e. Estimated cost of accident/incident (material and labor to repair/replace)

f. Impound Authority Name and Phone Number (as applicable)

g. Nomenclature of equipment and personnel involved in accident/incident

h. Corrective actions (taken or proposed)

i. Other pertinent information

Note: If requested by Government Personnel (PCO/ACO), the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records, until released by the investigating safety office. If the government investigates the mishap, the contractor and the subcontractors shall cooperate fully and assist the government personnel until the investigation is finalized and closed out.

6. Impoundment Procedures: The contractor shall establish written impoundment procedures, as part of their Safety and Health Plan. Impound data must be included in the Mishap Notification Procedures as applicable. As a minimum, the procedures must address:

a. Appointment of Impound Authority in writing (copy faxed to QAP and Safety Office)

b. Impound Authority e-mail address and phone numbers

c. Specific instructions (cordon, facility locked facility, etc.) to secure the site or government asset, to prevent tampering with the aircraft, site or government assets

d. Specific instructions or measures to ensure only authorized personnel directly involved in management, SAFING, troubleshooting, or repair of aircraft or equipment gain access to the impound site

e. Additional guidance is located within AFI 21-101, AFMC Supplement 1

T

9.3. APPENDIX C – Travel Request Form