AFI 63-501 PDF
Instruction (AFI) _IP, Management Of Aviation Critical Safety Items; Air Force Policy. Directive , AFMC Quality Assurance; and. Find the most up-to-date version of AFI at Engineering Additionally, this AF Instruction (AFI) implements the policies in management is contained in AFI , Air Force Acquisition Quality.
| Author: | Meztijar Duramar |
| Country: | Swaziland |
| Language: | English (Spanish) |
| Genre: | Business |
| Published (Last): | 15 September 2018 |
| Pages: | 388 |
| PDF File Size: | 16.47 Mb |
| ePub File Size: | 2.84 Mb |
| ISBN: | 179-4-72680-848-5 |
| Downloads: | 84771 |
| Price: | Free* [*Free Regsitration Required] |
| Uploader: | Samukazahn |
Address qualification and approval of special processes up front and early. Maintaining the plan includes changing it as necessary in response to either corrective actions or to changes in requirements and objectives for the process.
Identify issues and initiate and document corrective actions.
The responsibility for developing requirements down through the levels is generally 63–501 between the acquirer and the suppliers. Decide which project technical data and plans require version control, or more stringent configuration control, and establish mechanisms to ensure project data are controlled.
TO D 01SEP USAF DEFICIENCY REPORTING
Coordinate and obtain approval on major plans from relevant stakeholders. Develop criteria, processes and procedures for determination and disposition of nonconforming products to prevent its unintended use or delivery. This is typically the Government and might include both the project or program office and sponsoring office. Not every decision afu significant enough to require a formal evaluation process. Users should not rely upon the information given in this model alone and are therefore are encouraged to become familiar with referenced documents.
Deliverables from an external project e. When actual status deviates significantly from expected values, corrective actions are taken, as appropriate.
Typical life cycle choices include single-step acquisition, evolutionary incremental, or evolutionary spiral. Assessment team members begin their individual work by reviewing all available material for their area of assignment including the self-assessment data. Consider an iterative process of requirements refinement involving the suppliers and the end user as the design matures.
Design considerations should include ease of change, technology transparency and mitigating the risk of component obsolescence. Change requests address not only new or changed requirements e. Establish and maintain a disciplined process for handling of safety critical items, including identification of established technical authorities, quality assurance, and qualified manufacturers.
Document the plans, and coordinate with all stakeholders.
Stakeholders should participate in Provisioning Conferences and associated planning to ensure appropriate sustainment support will be available and timely.
A product is a work product that is delivered to the customer. The suppliers typically use peer reviews internally on selected interim work products during development, but the acquirer should not rely solely on these results. Implement technical standard work and process guidelines. Risks must be identified and described before xfi can be analyzed and managed properly. CMG1P2 Establish and maintain plans for managing the configuration of the product.
Risk identification and estimation of probability of occurrence and impact, particularly for those risks involved in meeting performance requirements, schedules, and cost targets, largely determine the acquisition strategy. Clear manufacturing readiness criteria should exist for each phase of the project and be agreed to by relevant stakeholders.
Periodically conduct architecture evaluations to confirm the continued suitability of the product architecture. Identify the policies which must be implemented to manage the failure modes which could cause the functional failure of ati product in operations e.
Track the status of change requests to closure. Include plans for managing data within integrated teams and 63-510 infrastructure required to manage data between the suppliers, operational users, and other relevant 63-051.
The type and extent of control applied to the supplier and the purchased product should 63-50 dependent upon the effect of the purchased product on the final product.
Additionally, the committee found throughout the study process that many of these concerns appear to continue to plague Air Force acquisition programs today.
Looking for other ways to read this?
DG1P5 Analyze and select product-component solutions that best satisfy the established criteria Description: CMG2 Establish and maintain technical baselines af managing change. Review the computing system architecture to ensure robustness, fault tolerance, reserve capacity and growth are addressed.
Air Force core software metrics size, effort, schedule, quality, requirements definition and stability, staffing, progress, and computer resources utilization should be used to track all software to be developed, integrated, and delivered.
Feedback The purpose of feedback is primarily three-fold. Posting Results – E Information is compiled as directed by local policy 63-051 procedures.
Provide sufficient data to support certifications.
Develop, coordinate and document validation criteria, methods and procedures. PG1 Establish and maintain estimates of project planning parameters PPG1P1 Define the project life cycle phases, milestones, and key decision points Description: Proactively seek opportunities for combined testing with the operational test agencies and oversight offices.
Care should be taken to ensure a practice is not omitted which upon closer examination may not be customarily considered for inclusion, but should be included to promote overall mission success. This provides a basis for acquisition process discipline, while balancing the need for flexibility, and tailoring to specific AF user needs.
For this tool to be afj successfully, it relies upon the candor of process participants in an environment of leadership support to improve the process. There is a continuous iteration developing increasingly detailed derived requirements as the multiple layers of a complex product are defined.