Background/Justification. There is an enduring requirement for Defence to provide an agile, interoperable and survivable maritime GEO INF capability that enables strategic, operational and tactical freedom of manoeuvre, which contributes to UK resilience, littoral theatre entry through timely data collection and maximising environmental exploitation. The SML has an enduring requirement to support Military Task 3 (MT3; Defence of the United Kingdom and Overseas Territories) and has a current Out of Service Date of April 2018. Outside its standing task and operational requirements, the SML (R) will have the new requirement to support the new Minewarfare and Hydrographic Capability (MHC) programme (through evaluation, operating and de-risking) by operating off board Autonomous Underwater Vehicles (AUVs). To meet the taut timeline of MHC there is an urgent need to have the SML (R) capability ISD on 01 April 2017, a year earlier than the current SML’s OSD. Due to the compressed timeline for an earlier ISD, the complexities of the capability support to MT3, the MHC programme and limited manpower resource, there is a need to out source the development work to generate an independent and objective URD and SRD. Activities to be Undertaken: Through stakeholder engagement and review of the MHPC URD / SRD generate a URD, then a SRD and finally develop the SRD into documents suitable for an Invitation To Tender format that supports either a Common Hull or Bespoke Hull procure e.g. develop fine tune SRD for contract specifications, publish function and measures of performance. See BMT Proposal FTC4243/PROPOSAL/01 dated September 2014 for detailed Statement of Requirement
Background/Justification. Under prior work four technical demonstrator units, designated Xxxxxx 3, were designed, built and delivered to Dstl. These units were tested. Experience gained has led to the compilation of a set of corrective items which could be addressed to improve the demonstrator system. A requirement for two further demonstrator units has been identified. Development of these two additional units is intended to take lessons into account, where practicable and affordable. There is an optional requirement for upgrade of the four existing Xxxxxx 3 units to a new design baseline, where applicable, to ensure compatibility across technical demonstrator models.
Background/Justification. The APED Minimum Operating Capability (MOC) project succeeded in delivering an improved ‘above neck’ physical protection capability for a limited number of Special Forces aircrew in early 2012 for CBRN CT Ops. This was achieved by building and fielding an advanced prototype of the Crew Systems Corporation (CSC) Lightweight Helmet (LWH) and Don in Flight Respirator (DIFR). The MOC capability, which has a life of 3 years, is being used on Chinook Mk2 & Mk4, NSRW and Lynx Mk7. In accordance with MAA regulations the equipment has to be fully supported throughout its service life. Gathering system reliability information, managing failures and updating ILS information are all key aspects to maintaining the platform clearances. The APED Full Operating Capability (FOC) project plans to build on the MOC success by extending the operating envelope and clearing it for use on a wider range of aviation platforms. The FOC project will also address a number of design / performance enhancements that could not be achieved in time for the 2012 delivery including a possible mass reduction exercise. Furthermore, the FOC project will seek to resolve any usability or reliability issues that are highlighted during the first year of MOC operations. Importantly, the FOC project will also include the provision of an improved ‘below neck’ capability that involves aircrew coveralls, boots / socks, and gloves. (Current ‘below neck’ equipments will run out, with no opportunity for re-provision, making FOC ‘below neck’ equipments essential for overall APED capability.) The APED FOC Assessment Phase Part 2 will commence in Sep 2012. Material developed (above neck) or supplied (below neck) will be tested and evaluated during an Assessment Phase to inform a Main Gate decision point currently planned for Apr 2014. The Assessment Phase will be run by the CBRN Delivery Team (DT) with specialist support being provided by Xxxx and QinetiQ. Subject to Main Gate approval, APED FOC will then replace the existing MOC systems in 2015 and the current ‘below neck’ capability. A Supportability management programme is required to raise the platforms RTS, support the in-service MOC capability and for the FOC Assessment Phase. Activities to be Undertaken: See Statement of Work at Annex A to this Tasking Form Deliverables: Outputs required, milestones, reports, software, demonstrations etc … See Statement of Work at Annex A to this Tasking Form Government Furnished Assets: GFI- DESK, IT FACILITIES, URD, S...
Background/Justification. Historically there has been the use of catalytic converters on vehicles in order to reduce the pollutant content of the emissions gases. This work is to research whether this technology can be enhanced to provide cleaner air. Activities to be Undertaken: To carry out rigorous and extensive testing of vehicles in both static and mobile environments, and to accurately record the measurements required. To produce a full emission map of the engines at different speeds and loads Of the two vehicles which need testing, they need to be of the following standards: A wheeled diesel engine military vehicle which is Euro 3 compliant. A wheeled diesel engine civilian vehicle which is Euro 6 compliant. It is envisaged that, once started, this testing should take no more than one working week per vehicle to be completed. A period of 20 working days will then be allowed to the supplier to produce the results in a yet to be agreed format. As a minimum the supplier MUST be able to test for the following: Gas concentrations: HC, CO, NOx (NO and NO₂), CO₂, O₂ In addition on VTEC: SO₂ and particulate matter Measurements: Engine RPM, Exhaust Volume. Speed, atmospheric conditions (i.e. temperature/humidity) for each test. In Addition Measurements on VTEC: Torque The following measurements would be desirable during the testing on PEMS: Engine Torque, Fuel Consumption, Particulate Mass/Size The work is to be carried out at the supplier’s location and the supplier must therefore have a suitable test track in order to allow the vehicles to reach operating temperatures and work under load. It is assumed that the work to be completed is in line with normal industry standards of recording and measurement, and in line with future legislative emission techniques. Both vehicles are to be operated using their standard supplied fuel and are to have had no specialist preparation work completed. The civilian vehicle will be a Ford Focus and this will be supplied by Dstl for the testing. If the supplier is able to provide access to a military vehicle this will be beneficial to be tasking and is the preferred option. The work is to be carried out at the supplier’s location and the supplier must therefore have a suitable ‘road’ test track in order to allow the vehicles to reach operating temperatures and work under various loads, speeds (up to a maximum of 70mph) and duty cycles. This testing is to be completed on moderate track conditions only (no severe suspension testing is required). Cold s...
Background/Justification. FSC Indicator 1.1.b requires that forest management plans and operations comply with state Best Management Practices (BMPs) and other forest management guidelines applicable to the forest, both voluntary and regulatory (see also Criterion 6.5). During the site visits, some District Foresters did not demonstrate a detailed understanding of applicable BMPs. While potentially understandable because they do not normally supervise harvest operations, management of an FSC group would be facilitated through a better understanding of BMPs. The same is true for seasonal interns or other staff conducting 5-year property inspections and logging contractors. REC 2009.1 We recommend that the Division of Forestry: 1) evaluate the need for additional BMP training for District Foresters; 2) develop and implement appropriate training programs for District Foresters, if warranted; 3) review and revise, as necessary, BMP training requirements for seasonal interns or other staff conducting 5-year property inspections, and 4) offer BMP training to logging contractors or support existing efforts by other parties in the State that provide such training. Reference FSC Indicator 1.1.b
Background/Justification. FSC Indicator 1.6.b requires that forest owners or managers document the reasons for seeking partial certification. The Division of Forestry has eligibility criteria for membership in the Classified Forest Program FSC certification pool. There may, however, be small areas of eligible, but unclassified, forests on parcels that are enrolled in the Classified Forest Program. The team believes that this would be a small acreage, but recommend that the Division identify such parcels on group member properties and encourage their enrollment in the Classified Forest Program.
Background/Justification. FSC Indicator 2.1.a requires that forest owners or managers document the legal and customary rights associated with the forest. These rights include both those held by the party seeking certification and those held by other parties. Based on management plans inspected to date and interviews with District Foresters, it appears that most legal rights are described in the management plan, including leases, easements, County roads, oil and gas xxxxx and lines, and County drainage easements. The team recommends, however, that the need to include these legal rights, as well as any customary rights, in the management plan for each parcel should be reinforced with District Foresters, industry foresters, and consulting foresters. REC 2009.3 We recommend that the Division of Forestry: 1) inform District Foresters, industry foresters, and consulting foresters of the need to document legal and customary use rights in the management plan; and 2) develop a quality assurance program for ensuring that such information is included in all management plans. Reference FSC Indicator 2.1.a
Background/Justification. FSC Indicator 3.1.a requires that on tribal lands, forest management and planning includes a process for input by an authorized tribal governing body. Tribal enterprises are known to be buying land in Indiana, and these properties may be enrolled in the Classified Forest Program. Tribal enterprise lands would be subject to the requirements found in Principle 3 that relate to tribal lands. REC 2009.4 We recommend that the Division of Forestry: 1) screen their Classified Forest Program database for lands owned by tribal enterprises and see what processes exist for soliciting input by an authorized tribal governing body. If such lands are found, we recommend that the Division of Forestry take all steps necessary to ensure compliance with relevant aspects of Principle 3. Reference FSC Indicator 3.1.a State of Indiana DNR agrees to implement the above-specified corrective action requests within the stipulated time-frame, unless modified by SCS. SIGNATURE Authorized Representative of State of Indiana DNR- Classied Forest Title Date Print or Type Name
Background/Justification. Engaging a single Industry Supplier through a Customer Friend Mechanism (CFM), rather than managing repetitive competitions against separate requirements, will reduce overheads, increase responsiveness and improve consistency of technical support deliverables that are required across the Operational Support Programmes (OSP). Activities to be Undertaken: See Attachment for detailed Statement of Requirement. Deliverables: Outputs required, milestones, reports, software, demonstrations etc … See Attachment for detailed Statement of Requirement.
Background/Justification. The term ‘Generic Vehicle Architecture’ refers to the open, modular and scalable architectural approach applied to the design of vehicle platforms to deliver the MOD’s desired operational, technical and cost benefits. The GVA approach exploits the output from the VSI research to understand the application of open systems and standards to vehicle design. Adoption of the GVA approach was accelerated in response to problems on current operations generated by poor on-board systems integration. It has at its core, a Defence Standard (23-09) that mandates the design and implementation of a common vehicle architecture covering the physical, power, electronic and HMI aspects across all vehicle fleets, both new and in-service. The aim of GVA is to improve system agility by providing the ability to integrate additional sub-systems and upgrade technologies more quickly and affordably. Higher levels of integration and commonality of sub-system designs also brings significant benefits to the training and logistic DLODs. Activities to be Undertaken: 1. GVA Data Model Development 1.1 Implement updates to the GVA Data Model and IDL Generator Raise LDM abstraction level Capture essential principles and universal patterns in application domain to reduce replication Model pervasive services in separate domains to simplify all domains Separation of “Type” vs “Actual” data to enable encyclopaedic data Use of associations to capture real-world linkages Normalisation of lists to remove fixed limits Use of UML operations instead of command data classes Use of UML state models instead of mode data classes 2. GVA Data Model Maintenance 2.1 Load and manage GVA information and data repositories on web based hosting service 2.2 Manage user access to the web based GVA Data Model development environment 2.3 Manage the configuration of the GVA Data model and the change control process 2.4 Update the GVA Data Model Support Documentation 2.5 Host a GVA Data Model User Group every 2 months 2.6 Host a MilCAN meeting and establish data exchange requirements 2.7 Attend the XXXXX GVA Meeting, in the capacity as DDS Middleware technical experts to brief on progress on the development of the GVA Data Model 2.8 Develop HTTPS access to the GVA Data Model 2.9 Provide a view of GVA Data Model usage, stability and maturity including: Visual map of model usage by geographical area Total accesses per month Pictorial view of module maturity and outstanding tickets View of approved users by organisation 3...
