Completed Tasks
What is a JIN?
JIN stands for Job Identification Number, and is simply a means of identifying a particular mitigation activity. In the case of the PMS Studies programme, these JINs are tasks that have been identified as mitigating risks that the MoD Integrated Project Teams (IPT) are exposed to.
Completed tasks at 16 March 2005 are:
JIN 1, 13, 22: Project Management 2000 - 2003
JIN 2: PMS Risks & Requirements: The foundation
task for the PMS Studies contract. Requirements & risks from
the Defence Procurement Agencies Warship programmes were assimilated,
analysed and prioritised into the core PMS risk mitigation programme.
JIN 3: Promotion and knowledge capture:
In order to achieve the maximum benefit at the outset of the PMS Studies programme it was agreed that the interests of the user community would be best served by a number of presentations to and by the PMS Studies team. These presentations were held at Abbeywood and at Portsdown and were aimed at the wider PMS community within the MoD. These presentations served two functions; firstly to generate buy-in within the community, and secondly to extract additional risks for the JIN 2 risk database.
JIN 4 : SDE Phase 1: Shared Data Environment (SDE) Phase 1: One of the key acquisition risks was the understanding and sharing of information within the PMS Stakeholder community, in Industry and the MoD. This task examined the requirements and feasibility for a web-site and shared data environment as a means of disseminating knowledge and lessons learned to the wider audience. Exostar Forum Pass was selected as the medium to mitigate the risk. See JIN 8
JIN 5: PMS Studies Workshops: The risk mitigation strategy
and risk report conclusions was presented to key PMS stakeholders
in DPA and to Industry partners. Generic acquisition & PMS
risks were discussed and enabled the setting of mitigation programme
priorities.
JIN 6: PMS Studies Database: Linked to JIN4, Knowledge
Capture and visibility to PMS stakeholders is essential to the
acquisition process. A prototype database, was developed to enable
knowledge capture from past and current PMS work. See
JIN 10
JIN 7: PMS Studies Cost Model: : Fundamental to the
Through Life Cost process is the need to understand PMS cost drivers.
A prototype cost assessment tool was delivered to allow user's
to examine effect's on unit cost and through life cost when defining
options or changes to PMS functionality, e.g. complement, software
integrity levels, automation levels, etc. See JIN 9 (below)
JIN 9: PMS Cost Driver Tool: Implementation of populated tool, issued to PMS stakeholders. A demonstration model of the Cost Driver Tool will be available through the web site.
View Cost Driver Tool (demonstration model only)
JIN 10: Knowledge Database: This task developed and
populated the knowledge database with 80 PMS related documents.
Stakeholders will be able to access the database via the public
web site. Restricted documents will now be provided on CD ROM.
View the Knowledge Database
JIN 11: Technology Assessment Tool: Implementation of populated tool, enhanced to indicate Technology Readiness Levels (TRL) of Industry COTS products and aid performance comparisons. Tool will be issued to stakeholders & available through web site.
View Technology Assessment Tool
JIN 12: Manpower Skill Sets: A workshop between TOPMAST
and PMS Stakeholders identified common understanding and agreed
the importance of Human Factors and Requirements Generation to
achieve system capabilities. The report has been issued to stakeholders
and will be available through the web site. New issues and concerns
will be analysed within JIN 18. JIN 14: Technology Assessment Tool Phase 1: Established how
COTS components of PMS technology could be analysed and compared.
Database allows either technology or requirements led analysis.
See JIN 11
JIN 15: FASM Pull-through: A review of the FASM research undertaken into advanced technologies and the requirements analysis to deliver a whole ship PMS in 2015+. This task will provide valuable lessons learnt and feeds into the PMS risk mitigation programme.
JIN 17: Non-functional Requirement Management: The IPTs have great difficulty in mapping non-functional requirements to PMS functional requirements and design. Standards have been reviewed to provide guidance and practical advice: ARM / ILS, COTS, Environmental, PMS Performance, Safety inc. Software, Security and Vulnerability.
JIN 18: Risk Refinement: This task provide lessons learnt from LPDR, Astute and other PMS, and is a continuation and extension of JIN 2, and includes extra risks identified as part of JIN 12. This task is essential to ensure that the mitigation activities meet the requirements of the IPTs.
Task is completed, recommendations have been made for the prioritised key risk mitigation tasks that have not been addressed to date.
These key risk areas are: PMS Integration, Data Fusion (task placed), Open Architecture and Flexible Systems, Identification of Source Data, Decentralised Control, Dormant Ship Requirements, Sensor and Decision Support, On-Board Training, Improved Knowledge of Target Environment. JIN 20: Requirements Generation Templates: This task is intended to develop a methodology that would allow the decomposition of a platform URD into an SRD. This method would allow the tracking of requirements, and facilitate acceptance.
JIN 21: CADMID Requirements Generation Templates: This task will determine how PMS requirements align with the MoD CADMID process (Concept, Assessment, Demonstration, Manufacture, In-Service, and Disposal).
JIN 24: Requirements Template Generation: JIN 20 was the first task associated with requirements generation and derived a process for URD to SRD mapping and gained stakeholder agreement on this process. This JIN details the actions necessary to continue the process for the production of a generic PMS requirements set by reviewing existing models, defining the core PMS functions through a workshop, and developing reusable models of these functions. These models will then be used to drive out requirements for the functionality of a PMS.
These requirements will be compared with the requirements database generated for the Future Attack Submarine (FASM) project and a damage control requirements database. Any gaps identified as part of this will be filled and the functional models will be updated.
PMS baseline functionality has been agreed with stakeholders.
Production of the functional model is complete.
Production of the generic PMS requirements is complete.
AAW, DSAC and MCAS scenario generation is complete.
Sequence diagrams for the above scenarios are complete.
Mapping of the functional activities to operational roles and tasks is complete.
Requirements have been reviewed and agreed.
Requirements set has been provided to PMS Team for utilisation in JIN 25 task.
All outputs have been delivered to MLS CG.
Final presentation to stakeholders was given on 20th October 2004.
Task outputs and presentation minutes issued to stakeholders on 11th November 2004.
JIN 26: CADMID Guidelines 2: This JIN details the requirements to produce the following set of guidelines (see JIN 23 for the 4 other guidelines).
Manning Optimisation and Training - guidelines are complete.
Functional Sequences - guidelines are complete.
Support Data For MDAL - guidelines are complete.
Incremental Acquisition - guidelines are complete.
The Human Factors Guidelines (manning, optimisation and training) document is now complete and ready for issue.
All CADMID documents will be available via the Warship Automation CD ROM, produced as part of JIN 8 activities.
JIN 29: Alerts Workshop: One of the significant Human Factors Integration risks associated with PMS operation is the alerting system methodology. This was highlighted in the JIN 2 Risk mitigation task.
To understand the issues that need to be addressed and enable a generic way forward, a workshop was held which covered:
Definitions of alerts terminology.
The military and commercial alerts “best practice” and classification society requirements.
An overview of the work carried out by MOD to date on this subject.
A review of IPT risks and requirements for alerting systems.
The adoption of COTS based alerting systems as distinct from bespoke systems.
Upon completion of the task, the following recommendations were made:
Update of NES 599 (Policy and Requirements and Design Guidance for Alarm and Warning Systems).
Provide guidance for:
Functional specification of a PMS alert system.
Specification for an alert user interface.
The acceptable balance between a COTS alert system and military qualification requirements.
View the JIN 29 Alerts Workshop presentation.
JIN 31: PMS to CMS Interface : Sustainment is a key factor in future navy concepts in which improved readiness and enhanced logistic operations will only be addressed via "more imaginatively commanded, adaptable, standardised, interoperable support that maximises and optimises the platforms and technologies available to meet requirements ".
These requirements are supported by the "migration of capability" required by the whole-ship approach advocated by PMS Studies. The purpose of this task is to provide a generic functional baseline for CMS & PMS interfaces and define an outline strategy to enable the delivery of the desired sustainability within the smart acquisition process.
Outputs from this task fed directly into JIN 24 and JIN 25.
Further work was recommended, this is to be discussed with MLS CG.
Task output contributes to the following:
Compliance with the Smart Acquisition principle being currently implemented within the MoD.
Being generic and therefore applicable to any platform or architecture.
Adopting a customer-driven focus that prioritises operational considerations.
PMS contribution to command in an operational context necessary for the appropriate delivery of platform and task force capability within the NEC (Network Enabled Capability) environment of the future.
JIN 32: Year 4 Project Management: Provides details of the 'way forward' on PMS Studies, providing a plan for activities over the next two years (assuming MoD agreement) of the contract.
A PMS Studies 'Road Map' document has been produced and issued to stakeholders. The report advises progress to date, benefits delivered and proposes mitigation actions for the two year option period, that include:
Continue identified risk mitigation activities identified in JIN 18 and JIN 29.
Share best practice with Tri-Service projects.
Production of a Requirements Demonstrator to enable Customer/Suppliers best practice in delivery of cost effective PMS.
'Road Map' was presented to the Steering Group on 6th September 2004. They were supportive of the proposed way ahead. Future Business Group took an action to assist MLS to write a forward to the Road Map document, to assist in achieving funding for the recommended mitigation actions within the optional two year contract extension period.
JIN 101: SIFFS Ship-board Intelligent Fire Fighting System: This task has been sponsored to examine the feasibility of developing intelligent on-board, fire fighting systems.
JIN 102: Intelligent Fluid Systems Feasibility Study: This task looks at developing and deploying "smart valve" technology on Royal Navy vessels.
JIN 106: Shipbourne Intelligent Fire Suppression System Operational Interfaces: A Human Factors (HF) centred task to provide an indicative context sensitive user interface for a SIFSS type system.
A HF consultancy has been established to ensure current and future concepts are captured.
An indicative user interface has been developed and shown to MESH.
Work on supporting documentation is complete.
The user interface specification is complete.
JIN 109: FLINCH Reconfigurable Systems: A task to look at the issues and requirements associated with 'FLINCH' systems, that enable the PMS to configure itself to minimise the possible effects of ship damage.
An initial workshop was held in January 2004 to define the scope of FLINCH requirements and a stakeholder discussion on FLINCH capability took place in March 2004.
The final FLINCH report has been agreed with MESH and was presented to stakeholders in November 2004.
BACK TO TOP |
