TUN_FY13_PBL_PES_PWS.pdf

PR FD2060-12-30506 PES for TUNNER PBL

PROGRAM ENGINEERING SUPPORT (PES)

PERFORMANCE-BASED WORK STATEMENT (PWS)

for

TUNNER

NON-AIRCRAFT WEAPON SYSTEM PER AIR FORCE POLICY

DIRECTIVE (AFPD) 10-9

Rev: 12 Oct 2012

The Air Force employs many diverse weapon systems in executing its global mission. The Chief of Staff United States Air Force designates systems as weapon systems and assigns each to a lead command. The Air Force Policy Directive (AFPD) 10-9 assigns weapon system management responsibilities to designated lead commands to ensure all requirements associated with weapon systems receive comprehensive and equitable consideration, and program-associated funding through the Future Years Defense Program as necessary. Lead command (AMC) designation establishes advocacy for weapon systems during their life cycle and clarifies responsibilities for all using and supporting organizations.

Prepared by

AFLCMC/WNZ SUPPORT EQUIPMENT AND VEHICLES ENGINEERING DIVISION

AGILE COMBAT SUPPORT DIRECTORATE

235 BYRON STREET SUITE 19A

ROBINS AFB GA 31098-1813

DISTRIBUTION STATEMENT C: Distribution is authorized to U.S. Government agencies and their Contractors (administrative or operational use) (5 May 2011). Other requests for this document shall be referred to AFLCMC/WNZDA.

1. DESCRIPTION OF SERVICES. This Performance-Based Work Statement (PWS) defines the tasks of Program Engineering Support (PES) for the Tunner non-aircraft weapon system (CAGE 98752 P/N 9032950). PES through a systems engineering approach provides the Air Force with the technical activities required to sustain the Operational Safety, Suitability, and Effectiveness (OSS&E) baselines of the Tunner system through proactive problem identification and problem resolution resulting in reduction of total ownership cost (RTOC) and improved readiness. Systems engineering provides the information technology (IT) solution for the integration and configuration control of the technical knowledge, development and maintenance of technical documents, development and maintenance of the data collection and analyses, resolution of system deficiencies and parts obsolescence, qualifications of parts/materials, and engineering-level field support. For Contractors other than the original equipment manufacturer (OEM), transfer of PES responsibility may occur at 10 months after contract award.

2. SERVICES SUMMARY (SS). The following table summarizes the performance thresholds for the most critical performance objectives of this effort.

Performance Objective PWS Paragraph Performance Threshold

System Review Board (SRB) Project Milestones shall be completed early or on schedule

4.1.1 85% of SRB Project Milestones completed early or on schedule per the baseline schedule; remaining 15% addressed in the Contractor’s variance analyses

Each SRB investigation in support of the Tunner SRB process shall be documented in an engineering report and posted on the website

4.2.6.2 80% of initial engineering reports shall be posted to Contractor’s website for Tunner Program Office viewing not later than (NLT) 3 working days after the unique SRB project number is assigned, and shall comply with the format and content requirements of Appendix B unless otherwise approved (see 4.2.6.2); the other 20% shall be posted within 7 working days

All mishaps reported citing injury or near injury of personnel, and any reports of failures or actions that had possible safety implications, require risk management

4.2.6.2 The initial draft of a project’s risk

assessment shall be included in the engineering report NLT 3 days after the unique SRB project number is assigned

3. GOVERNMENT FURNISHED PROPERTY AND SERVICES. The Government will provide the Systems Engineering Plan (Government), Engineering Drawings, OSS&E Plan, Tunner Technical Manuals, Time Compliance Technical Orders, Missing and Damaged Parts List, Overhaul Instructions Manual, Corrosion Prevention and Control Plan, Safety Assessment Report, Failure Modes Effects and Criticality Analysis, Unique Identification Plan, Base Code Reference List, Field Incident Reports, Nuclear Certification Checklist, Parts Shipped Data, Engine Hour Readings, Work Order Listing, As-Maintained List (AML) for each Tunner, Engineering Reports, Tunner Moves Document, and Definition of Terms (see Attachment 29 of the contract). The Government will provide one Tunner (see Attachment 28 of the contract) for Contractor’s use as an engineering test bed for verification of new changes. The Government will provide six 463L pallets, and six 463L couplers (see Attachment 28 of the contract).

3.1. Reporting loss of government property.

(a) Definitions. As used in this clause—

“Government property” is defined in the clause at FAR 52.245-1, Government Property.

“Loss of Government property” means unintended, unforeseen, or accidental loss, damage, or destruction of Government property that reduces the Government’s expected economic benefits of the property. Loss of Government property does not include purposeful destructive testing, obsolescence, normal wear and tear, or manufacturing defects. Loss of Government property includes, but is not limited to—

(1) Items that cannot be found after a reasonable search;

(2) Theft;

(3) Damage resulting in unexpected harm to property requiring repair to restore the item to usable condition; or

(4) Destruction resulting from incidents that render the item useless for its intended purpose or beyond economical repair.

“Unit acquisition cost” means—

(1) For Government-furnished property, the dollar value assigned by the Government and identified in the contract; and

(2) For Contractor-acquired property, the cost derived from the Contractor’s records that reflect consistently applied, generally acceptable accounting principles.

(b) Reporting loss of Government property.

(1) The Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application for reporting loss of Government property. Reporting value shall be at unit acquisition cost. The eTools “LTDD of Government Property” toolset can be accessed from the DCMA home page External Web Access Management application at http://www.dcma.mil/aboutetools.cfm.

(2) Unless otherwise provided for in this contract, the requirements of paragraph (b)(1) of this clause do not apply to normal and reasonable inventory adjustments, i.e., losses of low-risk consumable material such as common hardware, as agreed to by the Contractor and the Government Property Administrator. Such losses are typically a product of normal process variation. The Contractor shall ensure that its property management system provides adequate management control measures, e.g., statistical process controls, as a means of managing such variation.

(3) The Contractor shall report losses of Government property outside normal process variation, e.g., losses due to—

(i) Theft;

(ii) Inadequate storage;

(iii) Lack of physical security; or

(iv) “Acts of God.”

(4) This reporting requirement does not change any liability provisions or other reporting requirements that may exist under this contract.

4. GENERAL INFORMATION. In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

4.1 Program administration. The Contractor shall have overall responsibility for the conduct of Tunner PES in accordance with this PWS. Data in the Integrated Master Schedule (IMS), Earned Value Management System (EVMS), and Enterprise Resource Planning (ERP) system shall correlate.

4.1.1 Integrated master schedule. The Contractor shall develop, implement, maintain, manage and analyze an Integrated Master Schedule (IMS) for this contract effort. The IMS shall contain measurable tasks and their interdependencies. The Contractor shall develop task descriptions and schedules from this PWS. The IMS shall contain all critical milestones, measurable tasks, prerequisite events and activities, and their interdependencies as deemed necessary for effective management of this segment by the Contractor. Critical milestones shall include but not limited to: Contract Data Requirements List (CDRL) submissions and unique SRB Projects. The Contractor shall complete early or on schedule 85% of critical milestones. The remaining 15% shall be addressed in the variance analyses reports of paragraph 4.1.2.2. The IMS shall include major subcontractor activities, if any. For contractors other than the OEM, the IMS shall include the preparation of successful transfer of PES responsibility, to include the lower level objective criteria of 4.1.5. The Contractor shall develop descriptive listings for the above measurable tasks and milestones. The Contractor shall clearly depict critical elements throughout the entire period of this contract on selected schedule formats. Progress to date shall be based upon percentage of effort complete, whenever possible. Contractor’s schedule shall have the capability to roll up or roll down. In its reporting hereunder, the Contractor shall provide the necessary schedule and performance risk assessments, to include required program impact and related recovery schedules. (DI-MGMT-81861/T, X00C)

4.1.2 Performance and financial reporting. The Contractor shall utilize EVMS.

4.1.2.1 Compliance. All work shall be performed using a criteria-compliant EVMS that correlates cost and schedule performance with technical progress and program content activity.

Progress and problems shall be presented and discussed in periodic program management reviews. Technical and program content issues shall be covered in terms of performance goals, exit criteria, schedule progress and/or cost impact.

4.1.2.2 Reporting. The Contractor shall report monthly EVMS status using the Integrated Program Management Report (IPMR) formats, or Contractor internal documents which provide the same essential information and which have been approved by the Procuring Contracting Officer (PCO) or designated representative (rep). The Contractor shall report monthly the Contract Funds Status. The level of detail to be reported shall be at level 3 of the Contract Work Breakdown Structure (CWBS). The Contractor is responsible for developing CWBS levels 3 and below as necessary to accomplish all tasks. When change is necessary to the CWBS and CWBS dictionary, the Contractor shall update them. Contractor shall provide variance analyses that adequately explain all variances that exceed the specified variance thresholds of the data item description tailoring document; explanations clearly identify the nature of the problem, significant reasons for cost or schedule variance, effect on the immediate task, impact on the total contract, and the corrective action taken or planned. The PCO or designated rep will review the variance analyses and notify the Contractor in writing of any unacceptable ones. The Contractor shall not provide more than 3 unacceptable variance analyses per month; all unacceptable variance analyses shall be satisfactorily re-written and re-submitted by the Contractor within 20 calendar days of initial PCO or designated rep written notification. (DI-

MGMT-81861/T, X00C) (DI-MGMT-81468, X00D) (DI-MGMT-81334C/T, X00B)

4.1.2.3 Changes. The Contractor shall notify the Tunner Program Office in writing of changes affecting the accepted EVMS System Description. The Contractor shall provide to the Government all changes to the work breakdown structure (WBS) Dictionary. The Contractor shall provide its Program Work Breakdown Structure (WBS) and Contract WBS Dictionary 10 days after the award of the task order.

4.1.2.4 Access. The Government shall have access to pertinent records and data associated with the EVMS, including all records which directly feed, but are not officially a part of, the EVMS.

4.1.2.5 Documentation. The Contractor shall develop an EVMS System Description.

4.1.3 This paragraph is reserved.

4.1.4 Technical interchange meetings (TIMs). The Contractor and the Tunner Program Office shall meet weekly during this contract period, by telephone conference, video teleconference, or face-to-face, to discuss topics such as: change activity, the Contractor’s parts pipeline performance, maintenance actions performed, maintenance action trends, problem resolution, new requirements, and other issues or technical matters affecting Tunner field support and mission capability. The meetings should not exceed 1 hour in duration.

4.1.5 PES Ramp-Up and Progress/Readiness Reviews. For Contractors other than the OEM, the Contractor shall perform all tasks necessary to prepare for successful transfer of PES responsibility at 10 months, and shall brief on a regular basis their progress toward being ready for the transfer. The Contractor shall brief their final status (Readiness Review) to the Government at Contractor’s location 225 (+7) days (review start date) after contract award of the Contractor’s readiness to accept PES responsibility 10 months after contract award (see 1.).

Prior to the Readiness Review, the Contractor shall brief their progress toward the Readiness Review to the Government at Contractor’s location 60 days (+7 days), 120 days (+7 days), and 180 days (+7) after contract award. The Contractor shall use Power Point charts for the reviews and provide to the Government prior to or at the beginning of the briefing. The Contractor shall present charts, written processes, and hardware/software, for discussion and inspection, and the Contractor shall demonstrate compliance of the requirements, implementation of the processes, and establishment of employee training, for the following twelve key exit criteria elements (as a minimum):

1- IMS to include all major activities required to prepare for the transfer of responsibility, 2- systems engineering to include written processes for configuration management, change activity, qualification of parts, non-TO repairs, engineering field support, TO maintenance, performance determination and data reduction, and performance analyses of the Tunner system, 3- maintenance of the technical data , 4- SRB, 5- PLM system and Government access to the data, 6- rights of technical data , e.g., engineering drawings, engineering reports, technical orders, system performance analyses, system measurements, and system performance data, 7- Government technical baseline and what that means, 8- reduction in total ownership costs, 9- continuous improvement, 10- employees with the correct skills and tools, in place, 11- qualification of parts, and

12- approved SEP and CMP.

The Contractor shall report status for the twelve key exit criteria elements above by further breaking down each key element into lower level objective criteria; the Contractor shall update status of each objective criterion at each review by providing percentage of completion of each as compared to the IMS submitted within the proposal for this effort.

For qualification of parts, include review of written criteria for determining the appropriate type of qualification, and review in detail existing documentation and hardware (parts) of at least 3 actual current Tunner qualifications performed by the Contractor of each type of qualification.

The Contractor must receive approval from the Government to proceed after 305 days (or 10 months) after contract award. The Contractor shall record minutes documenting the reviews, and include the briefing charts in the minutes. Each review shall take no more than five days and the days shall be consecutive, and no more than 8 hours per day shall be allowed. (DI-ADMIN- 81250, X00E)

4.2 Systems engineering. The Contractor shall establish and maintain a systems engineering program. Systems engineering shall provide the integrating technical and managerial process that defines and balances performance, cost, schedule, risk, supportability, and security for the Tunner system throughout its life cycle. AFI 63-1201, Life Cycle Systems Engineering, is a good guidance document that may be used. The contractor shall use and maintain written systems engineering processes for sustainment of the Tunner system, and shall include an information technology architecture that ensures proper data management and process flows.

4.2.1 Systems engineering plan. The Contractor shall develop a Tunner Systems Engineering Plan (SEP). A SEP is the blueprint for the execution, management, and control of the technical aspects of the program for the purpose of helping technical managers develop their systems engineering approach—providing a firm and well-documented technical foundation for the program. A rigorous technical planning process forces thoughtful consideration and debate, allows for integration and coordination of technical activities across all levels of management, and results in a sound systems engineering strategy commensurate with the program’s technical issues, life cycle phasing, and overall objectives. This SEP is for the execution of systems engineering for the time period of this contract. The SEP shall address all systems engineering requirements of 4.2. The OSS&E Execution Plan of 4.2.3 shall be an attachment to the SEP.

The System Safety Program Plan of 4.2.16 shall be an attachment to the SEP.

The SEP shall include an SRB Project Development Process (SRB process) (see 4.2.6.2) for the development and verification of corrective actions, improvements, and new capabilities. The SRB process shall be presented in a chart or table format, and each process step/milestone shall be numbered and defined. The SRB process shall include as a minimum the following steps/milestones:

1- pre-initial investigation, 2- initial investigation or concept exploration, 3- root cause analysis or requirements analysis, 4- preliminary solution and cost estimate, 5- prototype build and test, 6- final design and logistics impacts and cost estimate, 7- preliminary technical data (i.e., engineering drawings, technical manuals, overhaul instructions, etc) development, 8- ECP/CCP development, 9- Air Force Configuration Control Board (CCB), 10- kitproofing, 11- release of technical data, and

12- implementation.

At the Contractor’s discretion, the Contractor may add more steps/milestones as necessary.

The Contractor shall change the SEP and processes as necessary for continuous improvement.

The SEP can reference other plans, processes, or documents, rather than duplicate same information in the SEP (DI-SESS-81785/T, X010) (DI-CMAN-81022C/T, X001)

4.2.2 Tunner Performance Specification. The contractor shall maintain the current Tunner Performance Specification (PS) for the 60K Loader Vehicle (SP1-9032950) as Air Force requirements change. (DI-CMAN-81022C/T, X001)

4.2.3 OSS&E. The Contractor shall comply with the Tunner 60K Aircraft Cargo Loader OSS&E Execution Plan (OSSE 60_EP), and change the plan and processes as necessary for continuous improvement. AFI 63-1201, Life Cycle Systems Engineering, addresses OSS&E and may be used as a guidance document. The Tunner Program Office will review the Contractor’s OSS&E program, to include processes, annually to determine compliance with the Contractor’s OSS&E Execution Plan. The review shall not exceed three working days at the contractor’s facility. (DI-

CMAN-81022C/T, X001)

4.2.4 Configuration management. The contractor shall establish and maintain a configuration management (CM) program, and develop a Configuration Management Plan (CMP) using AFPAM 63-128 as a guide. The CMP and processes shall be changed as necessary for continuous improvement. PCO or designated rep approval is required for CMP changes. The specific loader configurations shall be defined by the engineering data at all times. The Government technical baseline shall be: Tunner PS (SP1-9032950), Corrosion Prevention and Control Requirements (MISC1-9032950), Tunner 60K Aircraft Cargo Loader OSS&E Execution Plan (OSSE 60_EP), Tunner CMP, and the Tunner Overhaul Instructions (OI) Manual (9032950- OI). Changes to or violations of the Government technical baseline require Government approval by submitting Configuration Audit Summary Reports. The Contractor has the authority to make loader changes below the Government technical baseline (e.g., engineering drawings, parts substitutions) provided the Government technical baseline is not violated, and records documenting the changes and the specific loader configurations are accomplished. Parts substitutions shall be interchangeable with all other fielded Tunner loaders. Engineering Change Proposals (ECPs) shall be developed for new loader requirements when requested by the

Government. (DI-CMAN-80639C/T, X003) (DI-CMAN-81022C/T, X001) (DI-CMAN- 80858B/T, X011)

4.2.5 Item unique identification (IUID). The Contractor shall comply with MIL-STD-130, and the Tunner UID Plan (60K_UID_PLAN). The Tunner UID Plan shall be updated/maintained as necessary.

4.2.6 System review board (SRB) and engineering change activity.

4.2.6.1 System review board: maintenance and authority. The Contractor shall establish and maintain an SRB and associated processes. The SRB is a joint review board consisting of Contractor and Government personnel who meet weekly for the purpose of gaining insight of all technical activities of the program and directing technical activities associated with the unique SRB projects. The Contractor shall lead the SRB, but the Government has the final authority on technical decisions for all unique SRB projects and changes to the Government technical baseline. The SRB shall employ multiple disciplines from the Contractor personnel. The SRB will include Government representatives from the Tunner Program Office and AMC (A5QL, A4TE, and A4RV), and shall be conducted by telephone or video teleconferencing (VTC).

The SRB shall determine the approval authority for all changes (see 4.2.4 for Government technical baseline). If the approval authority is the Contractor, the Government’s only role is to enforce the contract and provide guidance. The SRB shall convene weekly, unless cancelled by mutual agreement. The Contractor shall record minutes of each SRB meeting and include the call center log inputs as an attachment to the minutes. (DI-ADMIN-81250A/T, X00E)

4.2.6.2 Change activity. Change is necessary for long term support of the Tunner system and shall be accomplished as required. Change activity occurs in two overarching categories: normal support projects (e.g., obsolete parts or diminishing manufacturing sources and material shortages (DMSMS), overhaul line support, technical support, and correction of technical data errors); and, unique SRB projects for the development and verification of corrective actions, improvements, and new capabilities (e.g., improved system performance, resolution of loader deficiencies, development of modification designs and technology insertions, development of RTOC solutions, and development of non-TO repairs). The Contractor shall utilize 5,000 man-hour equivalents per year to accomplish unique SRB projects; for non-OEM Contractors, this activity shall begin at the transfer of responsibility of PES and MM. These 5000 hours per year are in addition to man-hours required for normal support projects. The SRB shall direct the technical activities of the unique SRB projects in accordance with the SRB process, and the Government is the approval authority for all unique SRB projects.

At each SRB meeting, the Contractor shall present as a minimum the following: number of man-hour equivalents for unique SRB projects used to date and number scheduled for the remainder of the year; status of each unique SRB project; call center log inputs (see MM PWS, 4.3.2) since the last SRB; and, all changes to the Tunner technical data since the last SRB. The Contractor, with the advisement of the SRB, shall prioritize and adjust the unique SRB projects workload to ensure the Government receives the best value for the budget. The Contractor or Government, using any available sources, may provide potential candidates to the SRB for unique SRB projects approval. Potential candidates presented to the SRB and approved by the SRB for action shall be assigned a unique SRB project number immediately following the decision. The Contractor shall proceed in accordance with the SRB process (see 4.2.1) to accomplish the unique SRB projects. The SRB must approve the progression through each step of the SRB process; the Contractor shall not proceed to the next step of the SRB process without SRB approval. The Contractor may proceed in accordance with the pre-initial investigation step without permission from the SRB when a potential candidate is provided outside the SRB meeting; the pre-initial investigation results shall be presented to the next SRB meeting for approval. When a formal deficiency report (DR) from the Government is provided to the Contractor, the Contractor shall accomplish a preliminary investigation, and provide an initial response to the SRB within 24 hours. This may require the SRB to convene outside the normal schedule. The Contractor shall continue with the execution of resolving the DR using the SRB process. All change activities shall not result in compromising the OSS&E baselines, the Nuclear Certification, and the Air Transportability Certification.

Each investigation (pre-initial investigation, initial investigation) in support of the SRB process shall be documented in an engineering report. The engineering report shall be updated as the project proceeds through the process steps/milestones. The engineering report shall be in accordance with all requirements of Appendix B, Engineering Reports, Format and Content Requirements, unless other format and content requirements are approved by the Government.

All mishaps reported citing injury or near injury of personnel, and any reports of failures or actions that have possible safety implications, shall be investigated and risk levels determined.

Unacceptable risk levels shall be investigated and managed (corrected) through effective risk management. When performing risk management the Contractor should use Risk Management Guide for DoD Acquisition as a guide. The initial draft of the risk assessment and recommended risk controls shall be included in the engineering report no later than 3 days after the unique SRB project number is assigned.

The Contractor shall review all changes to the engineering drawings (loader design) to determine applicability to the Tunner Nuclear Certification using the Nuclear Certification Impact Statement (NCIS) checklist. If the change is applicable, the Contractor shall provide an NCIS.

The Contractor shall not implement any changes that impact the Tunner Nuclear Certification.

(DI-NUOR-81411/T, X004)

The Contractor shall accomplish a finite element analysis or update an existing analysis for all structural design changes. The Contractor shall provide a Contract Summary Report that shall include explanations of the changes and the results of the analysis. (DI-ADMN-80447/T, X006)

The Contractor shall revise the engineering drawings (CAGE 98255 PN 9032950 and its associated lists), and other applicable technical data, when accomplishing change activity of the

Tunner system. Release of the engineering drawings and other technical data shall be accomplished within 30 days of change approval. The Contractor shall correct errors (if applicable) in the Tunner technical data and add/delete drawings as required to maintain a complete technical data package that defines all of the latest fielded configurations. The Contingency High Priority Mission Support Kits (CHPMSK) list shall be updated as applicable when design changes are approved. The CHPMSK is a pre-positioned parts kit to support deployed Tunners. The kit arrives prior to the arrival of the Tunners providing most of the parts needed while in operation at that location. All engineering product definition data created as a result of this contract shall be considered a part of the technical data package. The engineering drawings shall be delivered in accordance with AF Product Data Specification drawing 9579776 (CAGE 98752). The Government shall have unlimited data rights to the engineering drawings.

(DI-SESS-81000D/T, X009)

The Contractor shall support and co-chair a Guidance Conference with WR-ALC/ENGLDC for engineering data within 60 days after contract award. The conference shall be convened for not more than one day at the contractor’s site and on a date agreed upon by the Government contracting officer and the Contractor. The Contractor shall brief the Government on their understanding of the engineering data CDRL requirements. The Government will review all CDRL requirements with the Contractor and provide guidance as necessary. The Contractor shall record minutes documenting the conference review, and include any briefing charts in the minutes. (DI-ADMIN-81250, X00E)

4.2.6.3 Qualification of Parts. The Contractor shall qualify new parts (e.g., substitute parts for obsolete parts or parts no longer available for purchase) as necessary to ensure the new parts will not degrade the OSS&E baselines and not lower TSSA below the requirement. The Contractor shall determine what is necessary to qualify the new parts. The Contractor shall write criteria for determining what type of qualification is appropriate for the various categories of new parts, e.g., the new part may be a very common commercial part and the vendor may be able to provide test data to support the commercial ratings, and therefore, that may be all that is necessary for qualification. Types of qualifications may include desktop review, vendor data review, first article test, demonstration, bench testing, and system test and evaluation. Use of written criteria and written processes will ensure consistent results.

4.2.7 Non-TO repairs. The Contractor shall document and archive all repairs performed by the Contractor not included in the Tunner TOs in the Metric Database (see 4.2.10). The Contractor shall also document and archive all known repairs performed by the Air Force not included in the Tunner T.O.’s in the Metric Database (see 4.2.10). The Contractor shall accomplish this activity by gathering, with Tunner Program Office assistance if necessary, any and all available information to document the incident and support the development of a repair procedure. The Contractor shall approve the repair procedure prior to its implementation. However, in instances when the field has performed unauthorized repairs, the Contractor shall investigate the unauthorized repairs and determine their validity. If a field repair is deemed an invalid repair, the Contractor shall develop and issue a corrective action repair procedure to correct the invalid one. The Contractor shall document these repair procedures and vault these procedures and any associated data in the Metric Database (see 4.2.10) for future use/availability by the Contractor and the Tunner program office. These non-TO repair procedures shall be available through a website set up by the Contractor for the purpose of easy access by the Tunner Program Office.

4.2.8 Field repair estimates. The Contractor shall provide estimates for field repairs when the Government requests same. Field repairs will be tasked separately if the Tunner Program Office needs the Contractor to accomplish the field repairs.

4.2.9 Engineering field support. The Contractor shall make engineering support available to the technical support team of the MM segment of this contract on a daily basis to address technical and/or safety issues that arise in the field. The Contractor shall ensure an initial response to the technical support team by the next business day 95% of the time. The remaining 5% shall occur within 2 business days. This support shall cover the electrical, mechanical, pneumatic, hydraulic and other disciplines as necessary. The term “daily basis” is defined as normal business hours (8 hours per day) during a normal business week (5 days per week) in the Eastern Time zone (USA). Engineering support may include travel to a requested location. Any time support is provided, the request for support, along with the recommended solution and final action, is to be captured in the metric database. These database entries will serve as the basis for systemic problem analyses and as input to the change activity process discussed in paragraph 4.2.6.2. The Contractor shall provide outputs to the Tunner Program Office in electronic form (Microsoft access database files or Microsoft Excel spreadsheets).

4.2.10 Performance determination and data reduction. The Contractor shall select, develop, and maintain software (tools) for generating monthly system measurements/metrics reports. The Contractor shall accept the Government OLVIMS data and collect/measure as necessary other data needed to determine compliance with the system performance metrics, and to support the publishing of the monthly and six-month cumulative Tunner System Sustainment Availability (TSSA) calculations. The Contractor shall establish and maintain a “Metric Database” to archive the OLVIMS captured and imported data provided by the Government, and other data mentioned above, which shall be included in the Contractor’s Product Lifecycle Management (PLM) (see 4.2.12). The Government shall have unlimited data rights to all data provided to the Government via the Contractor’s website and CDRLs. Data shall be segregable by region, individual location, registration number, metric/measurement, etc. The Contractor shall accomplish data reduction necessary to fully support the engineering analyses being accomplished to monitor and make necessary adjustments to the Tunner system to ensure the system complies with the system performance requirements. The Contractor shall prepare the source data, prepare the queries, and perform the calculations for the system performance measurements/metrics.

4.2.10.1 Engine-on hours and not mission capable for supply (NMCS). The Contractor and the Government shall work together each month to review and conduct error correction of the Government-furnished OLVIMS data to come to a mutually agreed-upon determination of the correct accumulated Tunner engine-on hours, direct labor hours, and NMCS hours. (NMCS is also known as VDP (Vehicle Down for Parts).

4.2.10.2 Performance analyses. The Contractor shall maintain and change as necessary for continuous improvement the processes and associated computer-based tools to facilitate the accomplishment of performance analyses. The Contractor shall conduct activities and investigations necessary to identify candidates driving negative trends to system performance and other lower level Tunner system parameters, and when necessary, make adjustments to the Tunner system to ensure compliance with the system performance requirements.

4.2.11 Technical order maintenance.

4.2.11.1 Technical orders (TO). The Contractor shall maintain the operations, maintenance, and illustrated parts breakdown technical orders, TOs 36M2-3-35-11, -12, and –14 and related checklists, by providing annual updates (complete revisions) throughout the entire contract period that reflect changes accomplished, errors found, and adjustments required to comply with system requirements. The Contractor shall process AFTO 22s per Air Force Technical Order System TO-00-5-1. All TO changes shall be managed by the SRB. TOs shall match the loader configurations in the field in accordance with the latest field modifications and TCTOs.

(TM-86-01N/T, X007 and X008).

4.2.11.2 Time compliance technical orders (TCTOs). The Contractor shall prepare three TCTOs each year to support the Tunner system in accordance with TM-86-01N/T and MIL-PRF-38804C (USAF). The Contractor shall submit TCTOs to the Government for approval and issuance.

(TM-86-01N/T, X007).

4.2.12 Contractor data system. The Contractor shall establish and maintain an integrated data system (also known as Product Lifecycle Management (PLM) system) to enhance the systems engineering process that enables the seamless flow of information across the organization. This system shall facilitate storage (vaulting and archiving of knowledge across the organization) and integration of technical knowledge. This system shall allow multiple users of various skills throughout the organization to access and operate on the inputs and outputs of other participants.

4.2.13 Travel in support of work tasks. The Contractor shall travel when necessary to support tasks herein.

4.2.14 Corrosion Prevention and Control Plan. The Contractor shall comply with the Corrosion Prevention and Control Plan (MISC1-9032950), and change the plan and processes as necessary for continuous improvement. (DI-CMAN-81022C/T, X001)

4.2.15 Reserved.

4.2.16 System safety program. The Contractor shall establish and maintain a system safety program in accordance with 4.3.1 through 4.3.8 of MIL-STD-882. The Contractor shall develop a System Safety Program Plan in accordance with MIL-STD-882 Task 102, and include as an attachment to the SEP (see 4.2.1). The System Safety Program Plan shall include a

Programmatic Environment, Safety, and Occupational Health Evaluation (PESHE) of the entire Tunner system to include, but not limited to, loader operation, loader overhaul line, parts supply houses, and parts manufacturing. The PESHE shall incorporate the MIL-STD-882 process. The PESHE shall include, but not limited to, the following:

1-identification of Environment, Safety, and Occupational Health (ESOH) responsibilities;

2- the strategy for integrating ESOH considerations into the systems engineering process;

3- identification of ESOH risks and their status;

4- a description of method for tracking hazards throughout the life cycle of the system;

5- identification of hazardous materials, wastes, and pollutants (discharges/emissions/noise) associated with the system and plans for their minimization and/or safe disposal; and

6- a compliance schedule covering all system-related activities for the NEPA (sections 4321-4347 of Sections 4321 et seq. of title 42, United States Code, “National Environmental Policy Act” and Executive Order 12114, “Environmental Effects Abroad of Major Federal Actions”, January 4, 1979).

The Contractor shall revise/update the Safety Assessment Report (SAR) as needed when change activity occurs. (DI-SAFT-80102B, X002)

4.2.17 Engineering test bed loader. The Contractor shall perform scheduled and unscheduled maintenance in accordance with the Tunner TOs on the Tunner test bed loader provided as GFP (see 3.). It may be used as a resource to support the accomplishment of tasks stated herein, e.g., testing unit for a new modification.

4.2.18 Quality assurance. The Contractor shall establish and maintain a Tunner quality program in accordance with International Standards Organization (ISO) 9001:2008 and the Tunner CMP.

4.2.19 Risk management. The Contractor shall establish and maintain a risk management program using the Risk Management Guide for DoD Acquisition as a guide. The risk management process identifies and mitigates future risks so they do not become issues. The process shall include risk identification, risk analysis, risk mitigation planning, risk mitigation implementation, and risk tracking.

4.2.20 Technical management and control. A technical management and control process shall be used for monitoring system performance, communicating status, and accomplishing corrective actions. If corrective action is required, these actions shall be defined and tracked to closure.

4.3 Green procurement program (GPP). GPP is a mandatory federal acquisition program that focuses on the purchase and use of environmentally preferable products and services. GPP requirements apply to all acquisitions using appropriated funds, including services, and new requirements. FAR 23.404(b) applies and states the GPP requires 100% of EPA designated product purchases that are included in the Comprehensive Procurement Guidelines (CPG) list that contains recovered materials, unless the item cannot be acquired:

a. competitively with a reasonable timeframe;

b. meet appropriate performance standards, or

c. at a reasonable price.

The prime contractor is responsible for ensuring that all subcontractors comply with this requirement.

4.4 Performance of service during crisis. The Functional Commander/Functional Director (FC/FD) has determined that this requirement is not Mission Essential (M-E) in accordance with DoDI 1100.22.

4.5 Inspection of services clause. The inspection of services clause from FAR 52.246 (as determined by contract type) gives the right to inspect contractor performance so long as it doesn’t cause undue delay to delivery of those services.

5. APPENDICES.

Appendix A. Applicable Documents The following documents of the exact revision listed below form a part of this PWS to the extent specified herein.

NAME OF

PUBLICATION

SECTIONS

APPLY

DATE OF

PUBS

TITLE OF PUBLICATION

CAGE 98752,

P/N 9032950

All drawings

Latest drawings

Engineering Drawings

SP1‐9032950 All Rev D, 13 Feb 07

Performance Specification for 60K Loader Vehicle

OSSE 60_EP All 10 Feb

Tunner Aircraft Cargo Loader OSS&E Execution Plan

MISC1‐

9032950

All Rev R, 19 Jan 2011

Corrosion Prevention and Control Requirements

TO 36M2‐3‐35‐

All 28 Jan 11 Operation and Operator Maintenance Instructions

TO 36M2‐3‐35‐

All 28 Jan 11 Maintenance and Overhaul Instructions

TO 36M2‐3‐35‐

All 28 Jan 11 Illustrated Parts Breakdown

9032950‐OI All 29 Apr 11 Tunner Overhaul Instructions Manual

60K_UID_PLAN All Rev B, 16 Dec 08

Individual Unique Identification Plan

MIL‐STD‐

129P(4)

All 19 Sep

Military Marking for Shipment and Storage

MIL‐STD‐130N All 17 Dec

Identification Marking of U.S. Military Property

AFI 63‐1201 All 23 Jul 07 Life Cycle Systems Engineering

All Sixth Edition, Version 1.0, Aug

Risk Management Guide for DoD Acquisition

MIL‐STD‐882E All 11 May

System Safety

TO 00‐35D‐54 All 1 Oct

USAF Deficiency Reporting, Investigation, and Resolution

TO 00‐5‐1 All 15 Aug

AF Technical Order System

Appendix B. Engineering Reports, Format and Content Requirements

FORMAT TEMPLATE: Engineering reports shall be formatted as follows:

ENGINEERING REPORT

Unique SRB Project (project number)

Title: (short title of project)

Date: (mo/day/year)

Introduction

History and Investigation

Life Cycle Cost (LCC) Impact

Summary and Conclusion

Recommendation

Future Actions Required

Closing Statement

References

Appendices

Contractor Signatures:

_____(signature)___________

Prepared By

(name/title)

______(signature)_________________

(Engineering manager name/title)

INSTRUCTIONS: Engineering reports shall contain contents as follows:

General Instructions: Engineering reports are very important for ensuring proper documentation for future use, and to ensure all necessary actions are taken. Good documentation will eliminate the “re-invent the wheel” syndrome, and ensure other areas are not forgotten such as QA, training, and technical data. These reports must be official Company reports with the company logo, and shall be dated and signed by the preparer and an engineering manager. The draft reports are not required to be signed. All projects assigned through the SRB shall be documented and closed by an official Contractor report. These reports shall be available through a website set up by the Contractor for the purpose of easy access by the Government Tunner program office, and the Government user. These reports shall be available on the website at the outset as a first draft. As the projects evolve, these reports shall be revised on a regular (weekly) basis so the latest information is available to the Government, and so the final report can be completed soon after the project work is done. The older report versions are not required to remain on the website. The first draft shall be available on the website within 3 working days after the project number is assigned. The final report to close a project shall be signed and available on the website within 5 working days after the SRB agrees to close the project. The final report shall include the closing statement seen below.

Other Instructions:

Unique SRB Project Number

Place project number at top as: Unique SRB Project # 1234.

Title

Provide a title that best describes the project in a few words preferably on one line.

Date

The first draft of this report shall be dated at the top of the page under the title and re-dated each time the report is revised. The report shall be reviewed each week to determine if new information is available, and if so, shall be updated and re-dated. However, if no new information is available, do not change the date of the report; wait until more information is available. The purpose is not to document task progress, but is to document results or information acquired. Also, please do not enter a date on the line or lines you add for each update. This will add unneeded clutter. If information in the report is discovered later to be incorrect, you should correct the error as soon as possible by deleting the error.

Introduction

State the preparer’s name and title. State the “start date” of this project. Describe the problem/issue in general terms. The overall topic is first introduced here, and the specifics are addressed later in the report. The remainder of the report shall correlate to this section. There is generally no need to write an extensive introduction. Four to eight lines should be sufficient most of the time, but use more when needed.

History and Investigation

In the first draft, document the history to date. Then, start a detailed account of all the information acquired from the steps taken to investigate the problem/issue, including: fact finding of the mishap, part failure, error in operations, etc.; determination of safety impact;

determination of OSS&E impact; identification of root cause; determination of the bottom line conclusion of any required failure analysis, stress analysis, weight analysis, cost benefit analysis, lab analysis, etc.; accomplishment of a preliminary design (if applicable). The analyses shall be provided in the appendices so that a full review of the assumptions and methodology can be accomplished. Document any discussions with the subcontractors/vendors. Explain any data provided by the subcontractors/vendors. Place the subcontractors/vendors data in the appendices. Consider changes to the technical data, such as T.O.’s, and engineering drawings, and to the design, QA, and training.

Quality Assurance/Configuration Control

The Contractor must provide the answer to this question: What has the Contractor done to preclude recurrence and does this problem/issue affect the rest of the fleet (or is it a one–of-a-kind)?

Life Cycle Cost (LCC) Impact

The Contractor must perform an LCC analysis to determine if there is a cost savings. We typically prefer a savings with a 3 to 1 pay back over the remaining life of the system or a payback accomplished within the next 10 years of life in order to justify implementing the change.

Summary and Conclusion

Summarize that learned in the “history and investigation” section and draw a conclusion.

Recommendation

Provide a recommendation(s) to resolve the problem/issue posed in the introduction. Address implementation through preferred spares (pull), or retrofit (push). Address any considerations for changes to T.O.’s, QA, training, and design to resolve the problem/issue. State the benefits of implementing the resolution. State the urgency of implementing the resolution. The LCC should support the recommendation; therefore, place that statement here also.

Future Actions Required

State the required actions necessary to implement the recommendation.

Closing Statement

When this project is closed, add this statement:

THIS PROJECT IS CLOSED PER SRB MEETING DATED (MO-DA-YR).

References

Any references stated above should be listed here. The following is an acceptable format to list the references:

L.H. van Vlack, Elements of Materials Science and Engineering, 6th Ed., Addison-Wesley Publ.

Comp., Reading, Mass., (1989), pp100-105.

Materials Science Handbook, 20th Ed., C.R.C. Press, Cleveland, Ohio, (1986), p. 986.

Appendices

The appendices section is available for analyses, data, sample calculations, definitions, references, specifications, etc.