HAL_PES_PWS.pdf

PR FD2060-13-30382 PROGRAM ENGINEERING SUPPORT

PROGRAM ENGINEERING SUPPORT (PES)

PERFORMANCE-BASED WORK STATEMENT (PWS)

for

HALVORSEN

NON-AIRCRAFT WEAPON SYSTEM PER AIR FORCE POLICY

DIRECTIVE (AFPD) 10-9

Rev: 4 Apr 2013

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 VEHICLE 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) (23 AUG 2012). 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 Halvorsen non-aircraft weapon system.

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 Halvorsen 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. Transfer of PES responsibility may occur at 12 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 Halvorsen 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 Halvorsen 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

Perform risk management for all mishaps reported citing injury or near injury of personnel, and any reports of failures or actions that had possible

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 safety implications

Deliver quality drawings to the Air Force

4.3.1.1 Any defects found shall be corrected

and re-submitted within 30 days.

No drawing submittals shall be rejected by the Government more than twice.

3. GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL, and SERVICES (GFP,GFE/GFM/GFS). The Government will provide the Halvorsen Technical Manuals, Government Systems Engineering Plan, Parts Shipped Data, Contingency High Priority Mission Support Kit listing of parts, Non-TO Repair Procedures, Prime Item Development Specification, and Halvorsen locations. The Government will provide one Halvorsen test bed for change verification, and the Contractor shall retain one of the first two Halvorsens overhauled as a manufacturing standard. The Government will provide six 463L pallets, and six 463L couplers.

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 Halvorsen 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. 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 other 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 other 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 Halvorsen Program Office in writing of changes affecting the accepted EVMS System Description. The Contractor shall provide to the Government all changes to the Contract Work Breakdown Structure (CWBS) Dictionary and shall require Government approval. The Contractor shall provide its CWBS and CWBS Dictionary within 10 days after the award of the contract.

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 Halvorsen 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 Halvorsen field support and mission capability. The meetings should not exceed 1 hour in duration.

4.1.5 PES Ramp-Up and Progress/Readiness Reviews. The Contractor shall perform all tasks necessary to prepare for successful transfer of PES responsibility at 12 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 330 (+7) days (readiness review start date) after contract award of the Contractor’s readiness to accept PES responsibility 12 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 90 days (+7 days), 180 days (+7 days), and 270 days (+7 days) 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 Halvorsen system, 3- reverse engineering and creation of the technical data package, 4- SRB, 5- PLM system and Government access to the data, 6- approved SEP and CMP, 7- qualification of new parts, and parts fit and function check of the 1,435 parts (see 4.2.6.3), 8- rights of technical data , e.g., engineering drawings, engineering reports, technical orders, performance analyses, performance measurements, and performance metric data, 9- Government technical baseline and what that means, 10- reduction in total ownership costs, 11- understanding of continuous improvement, and

12- employees, with the correct skills and tools, in place.

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 contract 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 Halvorsen qualifications performed by the Contractor of each type of qualification.

The Contractor must receive approval from the Government to proceed after 365 days (or 12 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 Halvorsen system throughout its life cycle. AFI 63-1201, Life Cycle Systems Engineering, may be used as a guidance document. The Contractor shall use and maintain written systems engineering processes. The Contractor shall use an information technology architecture to ensure proper data management and process flows. The Contractor shall establish a website for placing Halvorsen data for easy access by Government personnel, and on the website shall place the email address and telephone number for parts ordering and technical support.

4.2.1 Systems engineering plan. The Contractor shall develop a Halvorsen 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.15 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 associated 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 Prime Item Development Specification. The Contractor shall maintain the current Halvorsen Prime Item Development Specification (PIDS) (MP-SP-006, Rev 008) as requirements change and are approved by the Air Force. (DI-CMAN-81022C/T, X001)

4.2.3 Operational Safety, Suitability, & Effectiveness. The Contractor shall establish and maintain an Operational Safety, Suitability, and Effectiveness (OSS&E) program. The Contractor shall develop an OSS&E Execution Plan to be included as an attachment to the SEP.

The OSS&E Execution Plan shall make reference to the established OSS&E baselines and address the systems engineering processes necessary to preserve the OSS&E baselines throughout the operational life of the Halvorsen system. The Contractor shall ensure the processes are documented and in place, and followed. The Contractor shall ensure the processes are maintained throughout the life of the contract.

An OSS&E Execution Plan shall include the strategy for preserving the OSS&E baselines, maintaining the air transportability certification, establishing OSS&E metrics, and identifying data system feedback mechanisms. AFI 63-1201, Life Cycle Systems Engineering, addresses OSS&E and may be used as a guidance document.

The established OSS&E baselines are the requirements of Section 3 of the PIDS (MP-SP-006, Rev 008).

The Contractor shall change the OSS&E Execution Plan and associated processes as necessary for continuous improvement.

The Halvorsen 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. The Contractor shall record minutes of the review. (DI-CMAN-81022C/T, X001) (DI-SESS-81785/T, X010) (DI-

ADMIN-81250, X00E)

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, para 2.11.14.6, as a guide. The Contractor shall develop an As-Maintained List (AML) for each Halvorsen for all serialized parts, to include all parts with item unique identification (IUID), as parts are ordered from the field to perform field maintenance. The AML shall be maintained for each loader throughout the contract period and stored in the Metric database. The AML shall be placed in electronic form (Microsoft Access database or Microsoft Excel spreadsheets) on the Contractor’s website for download by Government personnel. The CMP and processes shall be changed as necessary for continuous improvement. The specific loader configurations shall be defined by the engineering data at all times. The Government technical baseline shall be: the PIDS (MP-SP-006. Rev 008), Halvorsen Finish Specification, Halvorsen OSS&E Execution Plan, Halvorsen CMP, and the Halvorsen Overhaul Instructions Manual. Changes to or violations of the Government technical baseline require Government approval by submitting Configuration Audit Summary Reports (X001). The Contractor has the authority to make loader changes below the Government technical baseline (e.g., engineering drawings and parts substitutions) provided the Government technical baseline is not violated, records documenting the changes are accomplished, and the specific loader configuration definitions are maintained. Parts substitutions shall be interchangeable with all other fielded Halvorsen 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 develop an IUID marking plan detailing the strategy to execute the marking requirements. The loader and any of its components for which the Government’s unit cost is more than $5,000, is serially managed, or the procuring agency determines is mission essential, shall have Unique Identification (UID) (also known as Item Unique Identification (IUID)) information permanently affixed on or near the respective identification plate(s), marked in accordance with MIL-STD-130. IUID information shall be included as both a bar code and human readable markings. The Contractor shall change the IUID marking plan and associated processes as necessary for continuous improvement. (DI-MGMT- 81803/T, X013)

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 Halvorsen 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 Halvorsen system and shall be accomplished as required. Change activity occurs in two overarching categories: normal support projects (e.g., 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; 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 Halvorsen 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, 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.

80% of initial (first draft) engineering reports shall be posted to the Contractor’s website for Government personnel easy access not later than 3 working days after the unique project number is assigned; 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 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 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 Contingency High Priority Mission Support Kit (CHPMSK) listing of parts shall be updated as applicable when design changes are approved. There are two listings, CHPMSK-30 (30 day kit) and CHPMSK-90 (90 day kit). The CHPMSK is a pre-positioned parts kit to support deployed Halvorsens. The kit arrives prior to the arrival of the Halvorsens providing parts needed while in operation at that location.

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 fail to meet performance requirements. 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. The Contractor shall purchase and/or make all 1,579 parts (see attachment 28 of the contract, filename Jan 2009 to Dec 2012 Cumulative Parts – All PNs only), and accomplish a parts fit and function check on a Halvorsen loader for all 1,579 parts (except for GFP parts of attachment 27 of the contract) prior to accepting responsibility of PES and MM.

4.2.7 Non-TO (NTO) repairs. The Contractor shall document and archive all repairs performed by the Contractor not included in the Halvorsen 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 Halvorsen TOs in the Metric Database (see 4.2.10). The Contractor shall accomplish this activity by gathering, with Halvorsen 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 Halvorsen program office. These NTO repair procedures shall be posted to the Contractor’s website for Government personnel easy access.

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 Halvorsen Program Office needs the Contractor to accomplish the field repairs.

4.2.9 Engineering field support. When engineering is necessary to support a field call, the Contractor shall provide 8/5 (8 hours per day and 5 days a week) worldwide engineering support to the technical support team of the MM segment of this contract and shall respond to requests for engineering support by next business day 75% of the time and the remaining 25% by the third business day. This support shall cover the electrical, mechanical, pneumatic, hydraulic and other disciplines as necessary. Engineering support may include travel to a requested location.

When engineering 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 Halvorsen 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 measurements/metrics reports. The Contractor shall accept the Government online vehicle interactive management system (OLVIMS) data and collect/measure as necessary other data needed to determine compliance with the performance requirements, and to support the publishing of the monthly cumulative performance calculations.

The Contractor shall establish and maintain a “Metric Database” to archive and supplement OLVIMS captured and imported data, 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 Halvorsen system to ensure the system complies with the performance requirements. The Contractor shall prepare the source data, prepare the queries, and perform the calculations for the performance measurements/metrics. See Attachment 23 of the contract for Metrics Reporting. The Contractor shall provide outputs to the Government in electronic form (Microsoft Access database files or Microsoft Excel spreadsheets) of the monthly reports from the Metric Database for performance verification.

4.2.10.1 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 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 Halvorsen performance, and when necessary, make adjustments to ensure compliance with the performance requirements.

4.2.11 Technical order maintenance.

4.2.11.1 Technical orders (TO). The Contractor shall maintain the current operations, maintenance, illustrated parts list, and manufacturer’s data technical orders, TOs 36M2-3-45-1, 36M2-3-45-2, 36M2-3-45-4, and 36M2-3-45–11, beginning immediately after transfer of PES responsibility to the Contractor until the new TOs are provided to the field. The Contractor shall maintain the current TOs by providing updates (supplements) as necessary to support the Halvorsen system. After approval of the new TOs, the Contractor shall maintain the new TOs by providing annual updates (complete revisions) as necessary to support the Halvorsen system.

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 approved configurations and TCTOs. The Contractor shall maintain TOs to match the latest loader part numbers. The Contractor shall place in the TOs the Contractor’s telephone number, website address, and email address for parts ordering and technical support. (TM86-01N/T, X007)

4.2.11.2 Time compliance technical orders (TCTOs). The Contractor shall prepare up to three TCTOs each year, beginning immediately after transfer of PES responsibility to the Contractor, to support the Halvorsen system in accordance with TM-86-01N/T and MIL-PRF-38804C (USAF). The Contractor shall submit TCTOs for approval and issuance. (TM86-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.

The Halvorsen Program Office shall have access to, and unlimited technical data rights to, engineering reports, performance data and analyses, and performance measurements/metrics for the purpose of enhancing future full and open competitions.

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

4.2.14 Finish specification. The Contractor shall develop a finish specification for the Halvorsen using the top coat, and primer requirements of OH PWS, Appendix B, 3.6. The specification shall address the requirements for the three color choices of green, tan, and black; different primers for aluminum versus steel; and, adhesion (wet) tape test. The Contractor shall include the finish specification in the TDP of 4.3. The Contractor shall change the finish specification and associated processes as necessary for continuous improvement. (DI-MFFP-81402/T, X014)

(DI-CMAN-81022C/T, X001)

4.2.15 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 Halvorsen 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 change the System Safety Program Plan and processes as necessary for continuous improvement. (DI-SESS-81785/T, X010)

4.2.16 Engineering test bed and manufacturing standard. The Contractor shall perform scheduled and unscheduled maintenance in accordance with the Halvorsen TOs on the Halvorsen loader used as an engineering test bed, and on the Halvorsen loader used as a manufacturing standard. The Contractor shall retain one of the first two Halvorsens overhauled as the manufacturing standard. The test bed provided as GFP may be used as a resource to support the accomplishment of tasks stated herein, e.g., testing unit for a new modification or change.

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

4.2.18 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.19 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 Government data rights. The Government does not own the original equipment manufacturer (OEM) technical data package (TDP) for the Halvorsen system; therefore, the Contractor shall accomplish reverse engineering to the extent necessary to support the accomplishment of all tasks of the contract. For the OEM or any Contractor that possesses the OEM TDP, reverse engineering includes the conversion of the OEM TDP to comply with CDRL X009; the Contractor shall deliver to the Government a TDP sufficiently capable of supporting the accomplishment of all tasks of the contract. The Contractor shall document the reverse engineering effort in the form of product drawings, models, and associated lists. The contract does not require the production of loaders. The contract is for the support of the existing Halvorsen fleet to include parts delivery to the field and overhaul line, loader overhauls, technical data maintenance, technical support to the field maintainers and operators, engineering to resolve loader deficiencies and DMSMS issues, repair procedure development, etc. The Contractor shall deliver a production level TDP for all reverse engineered items. There are loader parts/items that may never need to be replaced or overhauled such as chassis rails, lifting mechanism structure, and main deck structure. For these type items, complete detail design data may not be required, but instead these items could be depicted on the proper type of drawing or model using simple sketches without the design detail necessary to manufacture the item.

However, if at some point during this contract period, the need does arise for more detail to resolve a support issue or accomplish a contractual task, the Contractor shall accomplish the necessary reverse engineering and document the new data on the appropriate engineering drawing. As a minimum, the Contractor shall develop and deliver in not more than 12 months after contract award (see X009, blocks 12 & 13) complete engineering data for the 1579 parts listed in attachment 28 of the contract, filename Jan 2009 to Dec 2012 Cumulative Parts – All PNs only. The Contractor shall develop additional engineering data as required to support all requirements of the contract. The Contractor shall provide the Government unlimited data rights for the TDP.

4.3.1 Engineering data. The Contractor shall develop/ produce/maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. The TDP shall represent the approved, tested, and accepted configurations of the Halvorsen loader fleet.

TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of Materials (BOM). The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. All engineering product definition data created as a result of this contract shall be considered a part of the TDP and shall be delivered to the Government with unlimited rights. The CHPMSK listing of parts (see 4.2.6.2) shall be considered a part of the TDP and be delivered to the Government with unlimited rights. The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision K (CAGE 98752), and attached DD Form 1423 Block 16. (DI-SESS-81000D/T, X009)

4.3.1.1 Quality. Engineering data shall be rejected for non-compliance with CDRL X009. Any discrepancies found shall be corrected and re-submitted within 30 days. The Government will not be the quality assurance agent for the engineering data; the Contractor is required to accomplish quality inspection of the engineering data to ensure full compliance prior to submittal to the Government for review. When the Government reviews data submittals containing multiple files and numerous discrepancies are found, the Government may reject the entire submittal and return to the Contractor for correction. The Contractor shall re-inspect any submittals returned to them, correct all discrepancies, and re-submit the same submittal for a second review. The Contractor’s engineering data quality shall be such that no drawing submittals shall be rejected by the Government more than twice.

4.3.2 Engineering data guidance conference. The Contractor shall support and cochair a Guidance Conference with AFLCMC/EZGEM for engineering data within 60 days after contract award. The Conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the Contractor. The Contractor shall prepare an agenda and record the minutes of the Guidance Conference. The Contractor shall address, discuss, and provide status on the following:

a. Understanding of all CDRL requirements, applicable data item descriptions (DIDs), specifications and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. Contractor's drafting practices/procedures/TDP drawing formats/CAD programs.

e. The Contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

f. The role of subcontractors and vendors who may deliver TDP documents under this contract.

g. The Contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

h. Digital Technical Data Package (TDP) deliverables.

Guidance Conference may be held in conjunction with other meetings or conferences.

(DI-ADMN-81249A, X00A, DI-ADMN-81250A, X00E)

4.3.3 In-process review (IPR) of the TDP. The Contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the Contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the completion point of 100 drawings and models (out of the 1435 parts listed in attachment 28 of the contract) and not more than 4 months after contract award, and shall be held, when possible, in conjunction with other reviews.

The Contractor shall notify AFLCMC/EZGEM a minimum of 30 days prior to the anticipated date of completion point. The IPR shall focus on the Contractor's progress in the preparation of the TDP. The Contractor shall support and provide the necessary resources, i.e., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The Contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility. (DI-ADMN-81249A, X00A, DI-ADMN-81250A, X00E)

4.3.4 Relationship of Contractor with subcontractors/vendors. The Contractor shall levy on sub-contractors and sub-vendors the same requirements for Technical Data Packages (TDPs) as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program.

4.3.5 Engineering data updates and revisions. The Contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) supported and funded by this contract for the life of this contract and shall incorporate all changes in accordance with the following:

a. All engineering changes shall be incorporated into the applicable engineering data within 90 days after engineering release/Air Force concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

b. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c. All engineering changes shall be…