Before release of a formal Request for Proposal to build Weapons Systems, DoD must hold Industry Days to inform contractors about prototype technical requirements, acquisition goals and test/evaluation strategies, soliciting industry input for all weapons system prototype programmes and make sure communications between contractor and DoD are not limited as has often time been the case in past formal source selection process.
Prototype Test/Evaluation stakeholders must establish groundwork to achieve opportunity for free and open communications. In making deal. And emphasise the importance of prototype test/evaluation requirements such as use of test beds, virtual prototypes, incremental test/evaluation and fielding, having interoperable architectures and identification of specific ranges to resolve test/evaluation complexities and mitigate actual or anticipated risks to prototype programmes.
1. Use Prototype Test/Evaluation Strategy to emphasise importance of overall technical approach make system requirements available to industry, in accordance with DoD Component direction and guidance.
2. Discuss Prototype test/evaluation and any trade studies conducted during requirements generation process with emphasis to remain on resulting performance requirements and not on specifics alternatives.
3. Investigate potential prototype test/evaluation solutions responsive to requirements but DoD must avoid becoming fixated on certain solutions.
4. Be aware of situations in prototype construction where user is blinded with preference, acquisition team focuses on solution that works, and industry has exclusive solution it wants to sell.
5. Focus on establishing cost-effective prototype test/evaluation processes and events to generate technical and operational metrics so stakeholders make informed decisions.
6. Must have clear understanding of prototype system/subsystem requirements, encourage contractors to provide status updates of test/evaluation approach.
7. Address prototye test/evaluation strategies and how it was established to reinforce the importance of process/schedule valued by programme office
8. Provide for open one-on-one sessions to facilitate prototype construction but be careful to provide all contractors with equivalent information about requirements without giving away potential solutions offered by other vendors
9. Identify technical prototype areas of interest and encourage prospective vendors to provide information, insights, and suggestions to facilitate process transitions
10. Establish sound performance requirements and well-structured prototye test/evaluation approach and do not lose control of agenda and topics to industry
Top 10 Steps Define Field Level User Prototype Requirements/Constraints Impact Materiel Supply Transit Process for System Capability
Here we outline current intent, contents, and structure of challenging conditions in prototype system product support case studies. Over time, as smart logistics programmes implement/apply prototype models derived from acquisition case studies, more corresponding guidance will be issued by Site Visit Executive.
1. Prototype Availability/ reliability parameters must be explained and guide trade-off studies of mission capability and operational support, defining baseline against which the new system will be measured.
2. Prototype Performance factors need to be matched up with user needs into clearly defined system parameters and allocate/ integrate parameters to relevant disciplines needed to realise success.
3. Create prototype systems engineering attempts to optimise effectiveness, affordability of systems capability to make sure the question What are the user needs and constraints? is answered before designing the answer.
4. Execute top-level prototype programme plan for achieving required available/reliable to ensure requirements are achievable. Through understanding user needs and constraints, new capabilities begin to be defined.
5. Establish case for a materiel prototype approach to resolve gaps in capability to acquire quality products are required, balancing process of satisfying user needs while improving mission capability and operational support and adhering to scheduling constraints and justifiable acquisition costs.
6. Set aside time and resources for prtototype capability assessments to measure and characterise current operational experience, organise metrics and supply line performance to reach conclusions about the causes of shortfalls.
7. Imperative to understand prototype subsystem design complexity and influence on availability/reliability. Capabilities-based approach leverages expertise of all service directorate activities defining new capabilities.
8. Establish primary focus of prototype design to ensure joint force is properly equipped and supported to perform across disciplines to identify improvements to existing/new capabilities of training at Job Sites and define availability/reliability levels in category of materiel.
9. Establish goal to inform and share prototype information among decision makers tasked with design, buy, use, and system support to include user requirements, and how system will be used or potentially miss targets.
10. Structure assessments for description of prototype use/support location, constraints on what support is available for system and establish channels for making information available to decision makers
Top 10 Site Visit Executive Establish Coordination of Prototype Capabilities for Field Level Support
1. Authorises maintenance materiel allowance lists made available at job sites requried for prototype deployment activities
2. Provides guidance on procedures for prototype tech direction/review at each operational use functional level responsible
3. Directs prototype system design to reduce redundant, time-consuming, unnecessary reporting compatible at each operational field level
4. Provides on-site prototype performance improvement direct service/support to requesting activities
5. Plans, designs, develops and implements prototype decision support info systems affect life cycle
6. Provides prototype tech support to maintenance/logistics engineering and support training programme implement
7. Budgets for, funds and procures from industry all prototytpe materiel requirements
8. Allocates prototype materiel, refers requisition to meet requirements at stock points
9. Maintains, positions and provides materiel support for prototype system catalogs
10. Determines prototype system assets rework requirements of field-level use of components to be processed at job site
Top 10 Weapons Systems Assembly Sequence Planning Application for Mixed Prototype Trade-Offs
Assembly sequence planning for prototype products has always been a difficult task for engineers-- it is very difficult to formalise proofs of expert assembly planners. But automatic sequence planning systems can generate set of feasible sequences based on identified constraints.
Virtual Reality working space interface mixing the real prototypes and virtual prototypes provides a better working space for users to experience the realistic tactile experience of assembly operation and identify the assembly constraints.
Initial constraints are imported into the Automatic Assembly Planning System to generate the feasible sequences so planners can view and verify the feasible sequences in the virtual reality working space to identify new constraints and decide on requirements change criteria e.g., cost, number of orientations, etc.
Although the answers to these questions are very context dependent, basically we can make a decision based on the following aspects.
1. Design Strategy must obtain economies of scale in customised productions so standard components of prototypes have become very popular in manufacturing industry.
2. In mixed prototyping concept standard parts must normally be real components since they can be found easily in stocks.
3. For some fixed prototype designs that do not need to be changed much, can use real components through conventional rapid prototype technologies.
4. Customised parts must be evaluated and revised many times, virtual prototypes are used since flexible for modification.
5. During an assembly process impossible to connect two real prototype components using a virtual component to obtain realistic feedback-- cannot stack a real component on a virtual component.
6. Using the largest component of an assembly as a virtual part is not ideal if several other real and virtual parts are connected to it.
7. Parts where several prototype components are to be assembled, such as the base part, would serve better if they are real.
8. Some prototype workspace and assembly parts cannot be completely defined and simulation is so must use real components as much as possible.
9. If prototyping cost of some components is very high, try to use virtual prototypes even though designs are already fixed.
10. Prototype users can obtain more realistic assembly parts sensory feedback based on real components as compared to virtual components.
Top 10 User Interactions of Assembly Parts Load Into Prototype Simulation Scene Sample Position Constraints of Surrounding Objects
1. Detection of collisions between the manipulated/surrounding objects is continued until there is a collision.
2. Additional testing is made for possible assembly contacts between the surfaces of the collided objects.
3. Constraint is recognised if geometric surface elements of the collided objects satisfy conditions of a particular constraint type within a predefined tolerance.
4. Current implementation can recognise surface mating conditions such as against, coincidence, concentric, cylindrical fit and spherical fit.
5. When a constraint is recognised, feedback is provided to the user by highlighting the mating surfaces.
6. New constraint identification is ignored if the user continues to move the object to invalidate the condition for the constraint.
7. If user decides to accept the new constraint, the surface description of the mating faces and the type of constraint to be satisfied are sent to the constraint authority
8. Recognised constraints are satisfied by the constraint authority and the accurate position of the collided assembly part
9. When conditions allow for rigid body motions identification info is sent back to scene graph.
10. Information used by scene graph defines precise position of collided assembly part.
Prototype Test/Evaluation stakeholders must establish groundwork to achieve opportunity for free and open communications. In making deal. And emphasise the importance of prototype test/evaluation requirements such as use of test beds, virtual prototypes, incremental test/evaluation and fielding, having interoperable architectures and identification of specific ranges to resolve test/evaluation complexities and mitigate actual or anticipated risks to prototype programmes.
1. Use Prototype Test/Evaluation Strategy to emphasise importance of overall technical approach make system requirements available to industry, in accordance with DoD Component direction and guidance.
2. Discuss Prototype test/evaluation and any trade studies conducted during requirements generation process with emphasis to remain on resulting performance requirements and not on specifics alternatives.
3. Investigate potential prototype test/evaluation solutions responsive to requirements but DoD must avoid becoming fixated on certain solutions.
4. Be aware of situations in prototype construction where user is blinded with preference, acquisition team focuses on solution that works, and industry has exclusive solution it wants to sell.
5. Focus on establishing cost-effective prototype test/evaluation processes and events to generate technical and operational metrics so stakeholders make informed decisions.
6. Must have clear understanding of prototype system/subsystem requirements, encourage contractors to provide status updates of test/evaluation approach.
7. Address prototye test/evaluation strategies and how it was established to reinforce the importance of process/schedule valued by programme office
8. Provide for open one-on-one sessions to facilitate prototype construction but be careful to provide all contractors with equivalent information about requirements without giving away potential solutions offered by other vendors
9. Identify technical prototype areas of interest and encourage prospective vendors to provide information, insights, and suggestions to facilitate process transitions
10. Establish sound performance requirements and well-structured prototye test/evaluation approach and do not lose control of agenda and topics to industry
Top 10 Steps Define Field Level User Prototype Requirements/Constraints Impact Materiel Supply Transit Process for System Capability
Here we outline current intent, contents, and structure of challenging conditions in prototype system product support case studies. Over time, as smart logistics programmes implement/apply prototype models derived from acquisition case studies, more corresponding guidance will be issued by Site Visit Executive.
1. Prototype Availability/ reliability parameters must be explained and guide trade-off studies of mission capability and operational support, defining baseline against which the new system will be measured.
2. Prototype Performance factors need to be matched up with user needs into clearly defined system parameters and allocate/ integrate parameters to relevant disciplines needed to realise success.
3. Create prototype systems engineering attempts to optimise effectiveness, affordability of systems capability to make sure the question What are the user needs and constraints? is answered before designing the answer.
4. Execute top-level prototype programme plan for achieving required available/reliable to ensure requirements are achievable. Through understanding user needs and constraints, new capabilities begin to be defined.
5. Establish case for a materiel prototype approach to resolve gaps in capability to acquire quality products are required, balancing process of satisfying user needs while improving mission capability and operational support and adhering to scheduling constraints and justifiable acquisition costs.
6. Set aside time and resources for prtototype capability assessments to measure and characterise current operational experience, organise metrics and supply line performance to reach conclusions about the causes of shortfalls.
7. Imperative to understand prototype subsystem design complexity and influence on availability/reliability. Capabilities-based approach leverages expertise of all service directorate activities defining new capabilities.
8. Establish primary focus of prototype design to ensure joint force is properly equipped and supported to perform across disciplines to identify improvements to existing/new capabilities of training at Job Sites and define availability/reliability levels in category of materiel.
9. Establish goal to inform and share prototype information among decision makers tasked with design, buy, use, and system support to include user requirements, and how system will be used or potentially miss targets.
10. Structure assessments for description of prototype use/support location, constraints on what support is available for system and establish channels for making information available to decision makers
Top 10 Site Visit Executive Establish Coordination of Prototype Capabilities for Field Level Support
1. Authorises maintenance materiel allowance lists made available at job sites requried for prototype deployment activities
2. Provides guidance on procedures for prototype tech direction/review at each operational use functional level responsible
3. Directs prototype system design to reduce redundant, time-consuming, unnecessary reporting compatible at each operational field level
4. Provides on-site prototype performance improvement direct service/support to requesting activities
5. Plans, designs, develops and implements prototype decision support info systems affect life cycle
6. Provides prototype tech support to maintenance/logistics engineering and support training programme implement
7. Budgets for, funds and procures from industry all prototytpe materiel requirements
8. Allocates prototype materiel, refers requisition to meet requirements at stock points
9. Maintains, positions and provides materiel support for prototype system catalogs
10. Determines prototype system assets rework requirements of field-level use of components to be processed at job site
Top 10 Weapons Systems Assembly Sequence Planning Application for Mixed Prototype Trade-Offs
Assembly sequence planning for prototype products has always been a difficult task for engineers-- it is very difficult to formalise proofs of expert assembly planners. But automatic sequence planning systems can generate set of feasible sequences based on identified constraints.
Virtual Reality working space interface mixing the real prototypes and virtual prototypes provides a better working space for users to experience the realistic tactile experience of assembly operation and identify the assembly constraints.
Initial constraints are imported into the Automatic Assembly Planning System to generate the feasible sequences so planners can view and verify the feasible sequences in the virtual reality working space to identify new constraints and decide on requirements change criteria e.g., cost, number of orientations, etc.
Although the answers to these questions are very context dependent, basically we can make a decision based on the following aspects.
1. Design Strategy must obtain economies of scale in customised productions so standard components of prototypes have become very popular in manufacturing industry.
2. In mixed prototyping concept standard parts must normally be real components since they can be found easily in stocks.
3. For some fixed prototype designs that do not need to be changed much, can use real components through conventional rapid prototype technologies.
4. Customised parts must be evaluated and revised many times, virtual prototypes are used since flexible for modification.
5. During an assembly process impossible to connect two real prototype components using a virtual component to obtain realistic feedback-- cannot stack a real component on a virtual component.
6. Using the largest component of an assembly as a virtual part is not ideal if several other real and virtual parts are connected to it.
7. Parts where several prototype components are to be assembled, such as the base part, would serve better if they are real.
8. Some prototype workspace and assembly parts cannot be completely defined and simulation is so must use real components as much as possible.
9. If prototyping cost of some components is very high, try to use virtual prototypes even though designs are already fixed.
10. Prototype users can obtain more realistic assembly parts sensory feedback based on real components as compared to virtual components.
Top 10 User Interactions of Assembly Parts Load Into Prototype Simulation Scene Sample Position Constraints of Surrounding Objects
1. Detection of collisions between the manipulated/surrounding objects is continued until there is a collision.
2. Additional testing is made for possible assembly contacts between the surfaces of the collided objects.
3. Constraint is recognised if geometric surface elements of the collided objects satisfy conditions of a particular constraint type within a predefined tolerance.
4. Current implementation can recognise surface mating conditions such as against, coincidence, concentric, cylindrical fit and spherical fit.
5. When a constraint is recognised, feedback is provided to the user by highlighting the mating surfaces.
6. New constraint identification is ignored if the user continues to move the object to invalidate the condition for the constraint.
7. If user decides to accept the new constraint, the surface description of the mating faces and the type of constraint to be satisfied are sent to the constraint authority
8. Recognised constraints are satisfied by the constraint authority and the accurate position of the collided assembly part
9. When conditions allow for rigid body motions identification info is sent back to scene graph.
10. Information used by scene graph defines precise position of collided assembly part.
RSS Feed