GENERAL

1. The DDE is the implementation of the concept that all systems within the MOD that need information must be able to share information. The scope of the DDE is such that it enables Data Administration for the MOD and provides Data Management for the MOD at large. The following are the components that must be in place to enable this environment. It is important to recognise that, although described separately, each of the components is required to achieve the concept of the DDE. 

COMMON DATA DEFINITIONS

2. The lessons learnt from the monolithic, bottom-up approach used within DMIP (Data Management Implementation Project - now closed) of collecting and attempting to collate current data from multiple legacy systems and COTS packages indicate that any future approach should be incremental and pragmatic and should initially address the basic building blocks which are independent of business views and then build on this over time.[Definitions and Interfaces]

DATA INTERFACES

3. Although a single MOD data model may be the ultimate goal for MOD DM, the practicalities and the differing interoperability requirements of each Functional Area (FA) (A Functional Area is a defined business area within MOD, such as Logistics, Intelligence, Personnel etc) and between FAs demand that more than one interface standard is required along with the mechanisms needed to exchange that data. As an example, the Defence Logistics Organisation (DLO) needs to use DEF STAN 00-60 (a Defence Standard) today (and in the future Product Life Cycle System (PLCS)) to interface with industry and with Defence Procurement Agency. The mechanisms for physically moving the data also need to be addressed. The analysis of which type of replication mechanism is optimal for which data in which environment is complex. It is likely that there will be more than one type of replication mechanism to allow for the different scenarios.[Definitions and Interfaces]

COMMON ENCYCLOPAEDIC DATA

4. There is a requirement for all users to refer to the same set of encyclopaedic data to ensure consistency of information. The current situation is that many users are collecting the same encyclopaedic data from many different sources. This is inefficient and produces inconsistent information. There are only two formal organisations that has been formed to date to specifically source this data. These are: the Fleet Information Management Unit (FIMU) and Army Data Services.

TOOLS

5. Currently MOD procures tools from the very simple to the extremely complex both off-the-shelf and bespoke. To reduce overall MOD costs and to maximise the re-use of tools, there is a requirement to provide guidance to all areas of MOD who have some responsibility for DM on the choice of specific tool sets required for their particular activity.[Annex A to DM10]

DM IMPACT ON PROJECTS

6. Effective DM, which is one enabler for interoperability, will only be achieved by ensuring that individual projects comply with the underpinning DM standards and policies. Projects, therefore, need to take these requirements into account from the outset. The mechanisms required will result in the need to tailor the various project methodologies that are used. There are two issues that arise here. Firstly and fundamentally, constraining projects, even to a minimalist set of standards for the good of MOD as a whole, will mean that risk will need to be accepted by the MOD. Such an approach is contrary to the existing procurement policy and ethos. Procurement policy (through the Smart Acquisition Process) needs to recognise an MOD risk in providing corporate data. Secondly, policing of policies at project level is necessary to ensure adherence to DM standards and policies.[DM Handbook]

TRAINING/EDUCATION

7. DM is an essential enabler for interoperability. It needs management recognition and commitment including adequate resourcing. Such commitment will only be achieved if the impact of DM is understood. This requires training and education at all levels across MOD. The manpower resources required must be adequately trained for the tasks for which they are responsible.[Education Strategy]

INTERNATIONAL DIMENSION

8. The drivers for interoperability within and between the various business areas are different and are, in any case, continually evolving. In particular there are some areas where the requirements for interoperation with other UK Government departments or international partners may be equal to or greater than that for national military interoperability. It would be naïve to believe that all national data standards could be used internationally or vice versa.. The DDE allows for these differently prioritised views of interoperability. MOD should recognise the different drivers and attempt to minimise conflicting requirements. The associated management structure must also ensure it has adequate liaison with the international environment and other government departments in order to minimise the differences in data standards between the internal and external requirements for MOD.[Definitions and Interfaces]

POLICIES AND PROCEDURES

9. For the DDE to work there is a need for a minimalist set of policies, procedures and standards for DM to be put in place which are both applicable and adhered to across the MOD. These need to be accepted and conflicts in policy, such as the passing of risk to the contractor and the "COTS versus DM" dilemma, need to be reconciled. The set of policies and procedures, which must be applicable across the whole of MOD, should cover such topics as: data definition staffing procedures (including technical format), configuration management, procedures for the resolution of contention on data definitions and a guide for data definition owners. The output is a series of policy documents within Joint Service Publication (JSP) 329. (These will be referenced from the JSP600 series as Regulatory Instruments).[Policies]