Recommendations
Technical Progress
Provide a summary of the technical progress achieved in the period against the Second Level Plan on a work package by work package basis for each active work package.
Highlight deviations from the Second Level Plan, add reasons and actions to recover the situation.
Repeat for each active work package:
Work Package Number: WPA4 – Gap Analysis (BT Lead)
|
Actual Starting month: May 06
Predicted / Actual End month: Feb 09
|
Work Package Objectives:
The requirement analysis will be correlated with the results of the CIC and UbiCare projects to identify technology gaps which will feed into initial service and system specifications. During the course of the project, the Gap analysis will be repeated using inputs from prototypes and evaluation of initial user trials to identify major areas for improvement of the system and means to effect such improvements.
|
Description of work this period
BT
No direct activity has been undertaken on A4 but related activities on understanding patient profiles and the role of a community matron have been undertaken as part of C1. These activities will feed in to Deliverable D06, “SAPHE prototype architecture analysis”, workshops to be held in August and September 2007 (delayed from June 2007). BT also met with two Community Matrons in South East Essex to solicit further insights into the community matron role and the potential value of SAPHE.
Cardionetics - Work Package A4 Gap Analysis (ongoing)
Work has begun on identifying existing and emerging system specifications for the storage (i.e. file formats) and transmission (i.e. protocols) of biosignals data. There are no universally adopted standards at this time; however, the following have been identified as relevant:
SCP-ECG Standard Communications Protocol for ECG; this is referenced by the EuroNorm committee CEN/TC251, ref. PrEN 1064
EDF+ European Data Format; this is a digital file format that originated with EEG, but is being expanded to accommodate ECG
DICOM Digital Imaging and Communication in Medicine; being developed from X-ray imaging to a generalised format for storage and transmission of medical data
HL7 High Level 7; The V3 release attempts to develop a common information content model to ensure consistency; annotated ECG is a sub-section of this standard. For example header data requirements could include manufacturer name, software name, local/remote control state code, alert level code, last calibration time.
ISO 11703-10306 (IEEE 1073.1.3.6) Health Informatics communication – point of care medical device – ECG
FDA-XML the US Food and Drug Administration has specified an XML-based format for the representation of ECG and other data collected, initially as part of pharmaceutical trials.
|
Progress towards the Deliverables for this Work Package
Deliverable D06 - SAPHE Prototype Architecture Analysis – due Jun 07: Initial version of document was circulated to project partners prior to project meeting on 30th Jan. This document will be revised and developed in the forthcoming quarter when further inputs have been received from partners. Workshop on Architecture was held 15 June 07 to identify and address all issues in preparation for the end-to-end demonstrator for end July. This Deliverable is now complete, and work continues in WPs B5 and B7.
|
Summarise any variations from the Second Level Plan, giving reasons and action to recover situation if necessary.
- variations
- reason
- recovery plan
|
Description of planned activity for next quarter
IC - Ongoing research and analysis of existing and emerging technology solutions and commercial service offerings. Primarily this involves providing an understanding of needs, implementation challenges, and integration into current care system.
Docobo – Advisory inputs (when requested) into existing and emerging technology solutions.
|
Work Package Number : WPB1 System and Service Specification (BT Lead)
|
Actual Starting month : Jun 06
Predicted / Actual End month : Jul 07
|
Work Package Objectives:
Detailed technical and performance specification for the monitoring elements of the system and the ways in which they will interact. Detailed specification of the services required to deploy and manage large scale healthcare monitoring – includes communications, logging, training of personnel, etc.
|
Description of work this period
BT -
Good progress has been made on defining a greater level of specification for the end-to-end SAPHE system in collaboration with Philips and Imperial. Work in this area has now moved to WPB6.
Imperial – SAPHE System and Service Specification
Continued provision of input for development top level specifications of body sensing networks and vision based monitoring systems. Meeting held between Philips, BT and Imperial to define specifications for end-to-end communications within SAPHE system (this also feeds into contributions towards WPB6), with particular input from Imperial regarding middleware.
|
Progress towards the Deliverables for this Work Package
Deliverable D07 – Service Requirement for large-scale deployment – due Jun 07 – has been circulated for comment by partners and is available on the Website. Completion of this deliverable is anticipated during August 07.
|
Summarise any variations from the Second Level Plan, giving reasons and action to recover situation if necessary.
- variations
- reason
- recovery plan
|
Description of planned activity for next quarter
Development of Deliverable D07: Service Requirement for Large Scale deployment. Input of requirements relating to STB, body worn system and data analysis components. Needed to ensure a coherent system requirement spec. and to ensure agreement of requirements for trial implementation.
Imperial - Detailed specification of communication and middle ware based on UbiCare system experience.
BT - Development of Deliverable D07: Service Requirement for Large Scale deployment
Cardionetics - Development of wireless interface specifications ongoing
|
Work Package Number : WPB2 SAPHE Common Architecture (Philips Lead)
|
Actual Starting month : Mar 06
Predicted / Actual End month : Jun 08
|
Work Package Objectives:
Design and development of common node architecture for SAPHE, including hardware and communications and operating software. Particular emphasis will be placed on low-power RF design, development of analogue STSOM neural networks, network self-configuration and security issues. The work package will also extend into the design and specification of WAN interfaces.
|
Description of work this period
Philips – SAPHE Common Architecture Low Power Radio - Implementing star networking capability. New board design (compatible with Imperial BSN sensor boards) has serial, I2C and SPI interfaces. 20 Boards assembled ready for testing. Also defining protocols for defining communications with Mobile Hub and Sensors. Building an SDK for partners to use. Ultra Low Power Radio - RF Front end circuit design is proceeding to plan with the target tape-out date still set for November 2007. Work is currently underway on the RF design in the following areas: Re-working the earlier successful test chip circuits that were originally designed in Philips Semiconductors CMOS processes, for use with TSMC processes. During the re-working process, all the individual test circuits are being combined into a single silicon die. Additional circuits blocks are also being designed and simulated for remaining parts of the transceiver. These include some IF functions for the receiver (channel filters, limiters and miscellaneous glue functions), some transmit functions (modulator, Power Amplifier and miscellaneous glue functions) and the crystal oscillator circuits. Baseband: During this quarter, we have started to test some baseband IC's that we have received from the last Philips IC run. Results from this testing phase will not be available until the next quarter. In the meantime, design for the next baseband IC iteration is underway, in parallel with the measurement programme. Tape-out for this next iteration baseband IC will also be in November 2007 to coincide with the RF IC tape-out. Protocol: We are currently designing and refining a low power optimised master-slave protocol that allows up to 255 Slave nodes to be connected at any one time. Slave devices operate under ultra low power constraints, while the network master is assumed to be much less power critical. The system design covers the software design of the API, Management and Protocol Layers, and a Demo Master and Slave Application. In addition we are defining a hardware abstraction layer API, operating below the protocol, that serves to simplify and optimise control of the radio hardware itself. In terms of timing, we are currently on track to complete the majority of the protocol design in the next quarter. This will then be followed by a period of coding to allow the protocol to be run on the devices from the November 2007 tape-out. Imperial - SAPHE Common Architecture
Continued investigation of wireless standards (similar to 802.15.4) for common architecture, based on BSN node, performance testing for assessment underway. Redevelopment of packaging design for BSN node in progress.
|
Progress towards the Deliverables for this Work Package
Deliverable D04 - SAPHE Common Architecture Prototype - released March 07
|
Summarise any variations from the Second Level Plan, giving reasons and action to recover situation if necessary.
- variations
- reason
- recovery plan
|
Description of planned activity for next quarter
BT - Integration and performance testing of ZigBee nodes
Imperial - Development of SAPHE node based upon extensions of UbiMon BSN
Philips - Complete low power radio; continue development of ultra low power radio
|
Work Package Number : WPB3 SAPHE Body Sensing (Imperial DoC Lead)
|
Actual Starting month : Jul 06
Predicted / Actual End month : Aug 08
|
Work Package Objectives:
Use of common node technology for on-body sensing of activity and medical conditions. Autonomic sensing network with self-reconfiguration, self-healing, and context aware analogue implementation with STSOM neural networks.
|
Description of work this period
Imperial – SAPHE Body Sensing. Ongoing work on design and incorporation of sensors into wearable prototypes based on the developed e-AR earpiece (Lei Wang), including various experiments to test data recording using incorporated sensors. Experiments on motion/gait tracking using accelerometers and gyroscopes. Reconfigurable mixed signal array optimisation for SOM implementation, and modelling performed using Simulink. Development of software for channel selection for use with e-AR sensor programming.
Philips – Development of the mobile hub is continuing with work being done on the synchronisation of stored data with the set top box over Bluetooth. Algorithms and protocols have been developed following the proposed Bluetooth Medical Profile specification and should make the system Continua Compliant. New Mobile Hub hardware development has begun and PCB design has been completed and sent out.
|
Progress towards the Deliverables for this Work Package
Deliverable D08 – SAPHE Sensing Prototype – Due Sep 07 – Ongoing work on the design and incorporation of sensors into wearable prototypes
|
Summarise any variations from the Second Level Plan, giving reasons and action to recover situation if necessary.
- variations
- reason
- recovery plan
|
Description of planned activity for next quarter
Imperial - Development of body sensing system. Identification and continuing work to incorporate greater range of sensors e-AR earpiece design. Development of middleware to support system integration and communications
Philips - Complete Synch software; integrate radio with sensors; optimise mobile hub design
|
Work Package Number : WPB4 SAPHE Environment Sensing (BT Lead)
|
Actual Starting month : Sep 06
Predicted / Actual End month : Aug 08
|
Work Package Objectives:
Use of common node architecture for sensors around the home to determine activity and usage of facilities, e.g. motion, sound, vibration or temperature sensors. Emphasis on sensor message hopping for reduced power utilisation and network architecture that facilitates sensor inferencing, behaviour profiling, RFID applications, and support for self-configuration and self-healing.
|
Description of work this period
BT - WPB4 (and supporting WPB2)
Development of the ZigBee interfaces and network for environmental sensors has progressed well. A prototype ZigBee network has been programmed utilising the Integration DAMD1 modules upgraded with the latest Zigbee2006 firmware. Testing by both BT and Philips has identified range issues with the Integration USB dongles. This will be overcome by use of the DAMD1 modules (with a stub antenna) on the SAPHE hub (via serial port) in place of the dongles. This will also remove issues with a current lack of Linux support for the USB dongle. A data message protocol has been specified for the ZigBee network allowing a single sensor message to convey up to 83 bytes of sensor data. Support for fragmentation of longer data across multiple messages has also been provided.
Testing of the Tactex bed occupancy/pressure sensors has shown these to be of value for both simple occupancy detection and quality of sleep indication. An alternate commercial sleep analysis device available in Japan has been identified and it is hoped to obtain samples.
Imperial WPB4 – SAPHE Environmental Sensing
Development of PIR based motion sensor with ultra-low power radio for potential use within the SAPHE trial in order to minimise equipment costs. Ongoing enhancement of ‘blob’ sensors with focus on improvements for lower body tracking.
Philips - Set top box hardware has been through another design iteration and is now in its final version. Remote control still needs defining.
|
Progress towards the Deliverables for this Work Package
Deliverable D08 – SAPHE Sensing Prototype – Due Sep 07 – Ongoing development of ambient and environmental sensors and data storage solutions.
|
Summarise any variations from the Second Level Plan, giving reasons and action to recover situation if necessary.
- variations
- reason
- recovery plan
|
Description of planned activity for next quarter
Imperial - Integration of UbiSense/‘Blob’ sensor components
BT - Integration and performance testing of ZigBee nodes; Evaluation of third party sensors and integration methodologies.
Philips - Finalise software spec for set top box.
|
Work Package Number : B5 Sensor Fusion, Intelligent Data Mining and Trend Analysis (Imperial DoC Lead)
|
Actual Starting month : Dec 06
Predicted / Actual End month : Feb 09
|
Work Package Objectives:
Population database design, data mining, behaviour profiling, information inferencing from recorded data and prediction of adverse effects.
|
Description of work this period
Imperial – SAPHE Sensor data fusion, intelligent data mining & data analysis
Continuing progress and development of database functionality and access interfaces. Initial database architecture design complete. Document detailing SAPHE database structure and organisation of data along with XML format disseminated within the consortium. Work towards feature extraction, using multi-objective feature selection techniques, with focus on particular temporal features. Simulated datasets provided to Dundee for testing with appropriate visualisation techniques. WPB5 group teleconferences held in order to facilitate progress between partners and approach to initial development of analysis components agreed.
BT
An approach to the initial development of analysis components has been agreed along side the architectural specification in B1. It has been agreed that each partner involved in data analysis (Imperial, Dundee and BT) will hold their own database. The prime requirement will be that raw sensor data is stored as-is. Partners will be free to implement their own database preference. Initially it will be left to the sensor ‘owners’ to create analysis components and visualisation tools for their sensor(s).
Dundee - Sensor Fusion, Intelligent Data Mining and Trends Analysis
This has been our main area of effort over the past quarter.
We continue to use the ASP.NET with c# for development and the data being used is from the previous CitC trials.
The Dundas Chart software has been deemed to give the best results for the graphs required for the users, as well as having the capability present data help in OLAP data structures. However, because this is commercial software, it may be expensive to use in this project. For this reason, other graphing software has been investigated with some success. ZedGraph (http://zedgraph.org/wiki/index.php?title=Main_Page) is one which has shown to give good results in the early stages of using it.
Work in this area will continue as we look into other ways to represent data for the different end users. In particular, efforts will be made to produce prototypes that will work well on digital photo frames for informal carers.
|
Progress towards the Deliverables for this Work Package
Deliverable D09 – SAPHE Sensor Fusion and Data Mining Integrated System – due Feb 08. Work towards this deliverable is in the early stages. Regular partner teleconferences and discussions of methodologies and techniques will input towards the development and format of this deliverable in the forthcoming quarters.
|
Summarise any variations from the Second Level Plan, giving reasons and action to recover situation if necessary.
- variations
- reason
- recovery plan
|
Description of planned activity for next quarter
Imperial - Development of platform to integrate all data within dynamic system configurations. Particular focus on integrating sensor data from ambient and wearable sensors.
BT - Componentising of data analysis components form Care in the Community and Liverpool Pilot systems.
Dundee - Continue development for prototypes. Develop other ways of representing data, particularly the photo frame approach for informal carers.
|
Work Package Number : WPB6 Service Specification (BT Lead)
|
Actual Starting month : Mar 07
Predicted / Actual End month : Sep 08
|
Work Package Objectives:
Development of elements of service provision including communications systems, and implementation of interfaces between all users of the system. This will be based on the outputs of the initial service and patient engagement studies.
|
Description of work this period
BT (continues work initiated in WPB1)
With progress on defining the end-to-end SAPHE system in collaboration with Philips and Imperial, a generic, standards based approach is to be adopted as much as possible for messaging between system components. A Java Messaging System (JMS) implementation will be used for communications between the home (Philips hub), a central SAPHE network platform (BT) and other distributed analysis platforms (Imperial and Dundee) each with their own database receiving raw data streams via a JMS broker. An XML based text format will be used for the messages. This will be a lightweight schema based on that in use by Imperial for the e-AR sensor. A VPN implementation for securing home to network connectivity has been tested and specified together with scripts for auto-configuration of a BT HomeHub (ADSL modem).
Work is underway on the technical specification document D07 ‘Service Requirement for large scale deployment’, this will build upon the previous documents pre-D07 and SAPHE Data Comms that have circulated between partners. A first draft will be circulated by BT in July ahead of the next quarterly meeting. This is a delay from June 06 due to delays in agreeing elements of the system architecture.
Imperial – Service Development
Development of user interfaces for inferencing system for service providers, based on research in WPA3 and WPB5 is underway.
|
Progress towards the Deliverables for this Work Package
|
Summarise any variations from the Second Level Plan, giving reasons and action to recover situation if necessary.
- variations
- reason
- recovery plan
|
Description of planned activity for next quarter
Imperial - Integration of data mining platform into service provision system. Development of user interface for inferencing system for service providers
BT - Development of task plan for this workpackage. Specification of Network platform connectivity with non-SAPHE systems, i.e. Liverpool PCT and BT Vital Life platforms.
|
Work Package Number : WPB7 System Integration and Verification (Philips Lead)
|
Actual Starting month : Jun 07
Predicted / Actual End month : Feb 09
|
Work Package Objectives:
[It is anticipated that this will be based on three mirror verification set-ups at IC, Philips and BT. The verification is based on the specification from B1]
Complete integration of communications, sensing and service elements of the system. Verification of performance against detailed performance specification, both at technical and usability level, and modification of design elements.
|
Description of work this period
Philips – System Integration and Verification
This workpackage was due to start in June 2007. Some preparation work has already begun in Q5 with the specification of a demo for the July 2007 Project Meeting that shows aspects of all parts of the SAPHE system working together. This forces partners to address interfaces, protocols and APIs and show an end-to-end system working. This process should highlight at an early stage any critical issues with system integration.
Imperial – System Integration and Verification
Liaison between partners towards production of prototype system demonstrator (incorporating components developed to date) at Project meeting on 31st July.
|
Progress towards the Deliverables for this Work Package
|
Summarise any variations from the Second Level Plan, giving reasons and action to recover situation if necessary.
- variations
- reason
- recovery plan
|
Description of planned activity for next quarter
Philips - Finalise protocols and APIs of all components
|
Work Package Number : WPC1 User Trials (BT Lead)
|
Actual Starting month : Sep 06
Predicted / Actual End month : Feb 09
|
Work Package Objectives:
Design and subsequent implementation of effective trials to establish the value of systems for use within an active care environment. NB: this will have required significant early work with healthcare provider partners to establish the test protocols, gain the necessary ethical approvals, and identify suitable patients or elderly users.
|
Description of work this period
Imperial - User Trials
Further meetings to discuss approach to the trial have been held, involving Imperial College, BT, University of Liverpool and Liverpool PCT. These are beginning to identify the health conditions which should be targeted by the SAPHE approach and the processes for engaging appropriate local stakeholders. A process for feeding back local care system requirements to those responsible for technology development is being established. Key next steps are to finalise the target conditions, design the trial protocol and develop the LREC submission. It is still hoped that the LREC submission will be made in September 2007.
BT - User Trials
A further workshop has been held with Liverpool PCT to address engagement, SAPHE objectives and trial design. The workshop agreed the broad scope and purpose of the trial to explore the ability for a SAPHE system to assist community matrons and better support those with chronic conditions within the community. Andrew Sixsmith has started to lead an activity working with a group of Community Matrons to identify typical patient profiles and their current processes in order to determine requirements to steer the SAPHE technical design.
Cardionetics - User Trials
Specifying how the C.Net5000 will be integrated into the SAPHE system is to be developed. In particular, the wireless interface protocol is being investigated and specified. Alerts will be either be held in the Monitor and buffered, and reported in response to requests from the system (user initiated), or automatically transmitted from the Monitor; however, for the project, only the basic mode of operation may get implemented.
|
Progress towards the Deliverables for this Work Package
|
Summarise any variations from the Second Level Plan, giving reasons and action to recover situation if necessary.
- variations
- reason
- recovery plan
|
Description of planned activity for next quarter
Imperial - Liaison with Liverpool to help with trial design.
BT - Continued engagement, requirement capture and trial design with Liverpool PCT
Cardionetics - User trials, completion of prototype wireless communications
|
Work Package Number : WPC3 Cost Benefit Analysis and Deployment Business Models (IC BEIC Lead)
|
Actual Starting month : Sep 06
Predicted / Actual End month : Feb 09
|
Work Package Objectives:
Assessment of the value of the system in its various possible configurations to the several subpopulations within potential target user groups. Evaluation of business models for deployment of system to various target user groups. This will include both state organisations and private consumers.
|
Description of work this period
Imperial - Cost Benefit Analysis and Deployment Business Models
No further work carried out in this quarter, with the main focus being liaison with Liverpool. Data gathering will begin once the target conditions have been finalised.
|
Progress towards the Deliverables for this Work Package
|
Summarise any variations from the Second Level Plan, giving reasons and action to recover situation if necessary.
- variations
- reason
- recovery plan
|
Description of planned activity for next quarter
Imperial - Initial user and value model design and development and initial application using existing data. Redesign/re-application based on emerging data from SAPHE
|
Project Management And Collaboration
Summarise any management concerns and activities to recover the situation.
|
|
Detail any liaison activities with other projects and with the wider programme activities.
|
Management Group – weekly teleconferences and monthly progress meetings (ongoing)
WASP – EU common node project for wireless sensor networks (IC)
HaCIRIC – Health and Care Infrastructure Innovation (IC)
BiosensorNet – Novel biosensors and wireless networking technology (IC)
The Pervasive Computing Group have also recently won grant funding from EPSRC to develop Body Sensor Networks for Sports Applications (Sports-BSN), the grant will run from Jan 07 to the end of Jun 08 (IC)
Successful outline bid into MRC Lifelong Health & Wellbeing Centre proposal led by the Pervasive Sensing Centre
Visit to Nordic labs, Oslo, for outreach for SAPHE project, June 2007.
Co-ordination and submission of Q4 claims to DTI monitoring officer
Identification of Project Deliverables for publication outside of consortium (ongoing). This task will possibly take some time as Deliverables that have been identified will require some editing by their owners (Imperial, Philips and BT).
Next version of SAPHE Exploitation plan in development with inputs from consortium (led by management team) following attendance and feedback from DTI workshop on 19th June (Philips attended).
BEIC staff have linkages with the Platform for Assisted Living – launched 19 July 2007 in Birmingham
|
Detail any publication or other dissemination activity.
|
The second SAPHE Steering Committee Meeting took place on 6th March 2007. The meeting covered project progress to date with a focused review of the scenarios and the SAPHE system in terms of maximising patient compliance. Also discussed were trial systems and costs, with consideration of security and trust issues, and future engagement with stakeholders. Notes from the meeting are available from: http://ubimon.doc.ic.ac.uk/saphe/public/SAPHE_SC_Mtg_6-03-07_notes.doc
Pervasive Computing Group at Imperial College have been preparing their interactive exhibit for display at the prestigious Royal Society Summer Exhibition 2 – 6 July 2007. The theme of the exhibit will be Body Sensor Networks, and is expected to attract high levels of public, academic and media attention.
Keynote presentation given by Prof. Yang at WOWMoM Conference on ‘From Theory to Practice in Wireless Sensor Networks 2007’, Helsinki, Finland.
Development of Pervasive Sensing Centre initiative at Imperial College, led by Prof. Yang and with cross-departmental collaboration, including: Department of Computing, Institute of Biomedical Engineering,
|
Milestone and Deliverable Status
Summarise the composite project progress against all project milestones and deliverables, noting any discrepancies against the Second Level Plan and action to recover situation if necessary.
Use Green text for completed, Red for late and Blue for items due in the next quarter.
Ref
|
Title
|
WP
|
Responsibility
|
Due Date
|
Actual Date
|
Comments
|
M1
|
Delivery of Top Level Requirements to Steering Committee
|
A1/M&A
|
Imperial College/BT
|
Jun 06
|
Sept 06
|
Delayed as needed to complete D2 and Vision document, and also had difficulties with availability of SC members for meeting during vacation period
|
M2
|
Delivery of Top Level Technical Specification (Internal)
|
A1/B2
|
Imperial College/BT/Philips
|
Sept 06
|
Jan 07
|
Internal document ‘pre-D07’ completed and circulated to SAPHE consortium Jan 07
|
M3
|
Complete User and Trial System Spec. And Outline Trial Design: Steering Committee Presentation
|
C1-C3
|
BT & Imperial College
|
Mar 2007
|
N/A
|
This milestone is delayed to Sep 07 as a result of need to resolve issues with Liverpool PCT and review of essential timing of stages in trial design and approval processes
|
M4
|
System Prototype: Internal and to Trial Partners
|
B1-B7
|
All
|
Sep 2007
|
N/A
|
First end-to-end demonstrator made at project meeting 31 July 07
|
M5
|
Completed and Verified System and Trial Approvals: Steering Committee Presentation
|
B1-C3
|
All
|
Feb 2008
|
N/A
|
|
M6
|
Trail Start: Internal and Trial Partners
|
C1-C3
|
BT & Imperial College
|
May 2008
|
N/A
|
|
M7
|
Trial Completion, Initial Findings and Trial Approvals: Steering Committee Presentations
|
C1-C3
|
All
|
Dec 2008
|
N/A
|
|
M8
|
Final Report: Workshop
|
All
|
All
|
Feb 2009
|
N/A
|
|
|
|
|
|
|
|
|
D1
|
Level 2 Planning Document
|
M&A
|
Imperial College
|
Jun 2006
|
May 2006
|
Completed and submitted, however some revisions need to be done to complete the plan in the recently released I3.0 template
|
D2
|
Service and End User Requirements
|
A1
|
BT
|
Sept 2006
|
Aug 2006
|
Completed and submitted.
|
D3
|
Details of Specification model scenario
|
A2
|
BT
|
Oct 2006
|
Jan 2007
|
Completed and submitted, although slightly later than originally planned
|
D4
|
SAPHE Architecture Prototype
|
B2
|
Philips
|
Jan 07
|
Mar 07
|
Completed and submitted although slightly later than originally planned
|
D5
|
HCI Trust and User Engagement and User Acceptability
|
A3
|
Philips
|
Feb 07
|
Feb 07
|
Main part of D05 was submitted in Feb 07, Subsequent deliverables against this workpackage will be numbered e.g. D05a, D05b, etc and will probably be submitted in Q5 (Jun 07)
|
D6
|
SAPHE Prototype Architecture Analysis (Workshop)
|
A4
|
BT
|
Jun 07
|
Jun 07
|
First architecture workshop held on 15 June 07 – this work continuing under WPB5
|
D7
|
Service Requirement for large scale deployment
|
B1 (B6)
|
BT
|
Jun 07
|
|
Draft document currently available for comment on website: due for completion end Aug 07
|
D8
|
SAPHE Sensing Prototype
|
B3 + B4
|
Imperial College & BT
|
Sep 07
|
|
|
D9
|
SAPHE Sensor Fusion and Data Mining Integrated System
|
B5
|
Imperial College
|
Feb 08
|
|
|
D10
|
Trial Preparation and approval
|
C1
|
BT
|
Feb 08
|
|
|
D11
|
Pre-trial cost benefit deployment models
|
C3
|
Imperial College
|
Apr 08
|
|
|
D12
|
SAPHE Final Architecture
|
B2
|
Philips
|
Jun 08
|
|
|
D13
|
Affective HCI
|
B6
|
BT
|
Jun 08
|
|
|
Updated Schedule
Provide an updated Gantt chart for the entire project as an attachment if necessary.
Project Spend Profile
Attach the latest Project Financial Spreadsheet with up to date actual and forecast expenditure.
Explain the reasons for any deviations in spending from the baseline or previous forecast expenditure.
|
The SAPHE Project Spend Profile for Q4 Spend Summary shows some deviations from the baseline, these are:
Overspend on labour – this is largely due to a reduction in overhead rates for BT and Philips, which has enabled them to allocate more funds to labour costs (also reported in Q3 and Q4)
Underspend on overheads – see reason above and also reason below for Philips’ overspend on Subcontracts. Unfortunately, because the Project Spend Profile spreadsheet does not allow an ‘over-ride’ of the overhead rate after this has been entered into the baseline figures, a flag for incorrect overhead rate will show on the BT and Philips partner spreadsheets, even though the funds budgeted for overheads (rates have been reduced by both partners) can now be spent on labour costs.
Underspend on materials – this is a relatively small difference and is due to a reallocation of some materials costs by Philips to subcontracts, and the purchase of lab furniture by Imperial (see below)
Overspend on capital – this is due to the purchase of essential lab furniture by Imperial (reported in Q2 and Q3), not foreseen at the time of project planning, but required for the permanent trial environment at the IBE which has had to be reported under capital and not materials.
Overspend on subcontracts – this is due to internal staffing reallocations at Philips, which has meant that a number of Philips’ SAPHE project staff have had to be subcontracted from Philips APTEC (also reported in Q2 and Q3)
Overspend on other – see note for Philips below.
Philips: Unspent funds from Q1 and Q2 have been moved to Q12 by Philips to Forecast Other 1 costs to cover unforeseen trial costs at the end of the project (this could be materials and labour/overheads, but cannot be accurately identified at this point). However, this will be revised if there is no evidence that funds will be needed for the trial in Q12. David Walker (Philips) has expressed confidence that the full amount committed by Philips will be spent during the project duration.
University of Dundee have redistributed their project costs evenly between Q5 and Q11, as it is considered that this will reflect accurate project expenditure given current circumstances (see expenditure in Q4 for reference). Figures will be revised if future expenditure does not accurately match these figures. Dundee have also confirmed that their budget for ‘Other’ costs “is a provision for unforeseen costs that would not fall under any of the other headings such as administrative costs or the costs of hosting meetings, or running trials and focus groups.”
Docobo: [please refer to note on Docobo’s future contribution to the project in the Q4 report]. Due to high internal workloads and lack of internal resources, Docobo have been unable to provide any contributions to the project in Q4 and Q5 although we have maintained contact at a lower level. For this reason, there is no expenditure reported on the Project Spend Profile for this partner in Q5. Discussions between the management team and Docobo have identified a number of activities with relation to WPA4, WPC1 and WPC3 that will maintain engagement of Docobo with the project, with the same final level of expenditure as originally budgeted. The unspent funds from Q4 have been redistributed between Q6-Q11 to reflect this change in expenditure in the Project Spend Profile Forecast for Docobo.
|
Updated Project Risk Register
Work Package
|
Responsibility
|
Risk
|
Likelihood
(L/M/H)
|
Impact
|
Technical/ Commercial
WPA1 – 4, WPB1 – 7
|
BT, Imperial DoC & BEIC, Philips
|
Inability to overcome user privacy and security issues as defined by user specification research
|
M
|
User resistance to system; ultimately, could inhibit approval for trial
|
Technical
WPA3 & WPB6
|
BT, Imperial BEIC, Philips
|
Reliability and usability -
|
M
|
User resistance to system; ultimately, could result in trial becoming unviable
|
Regulatory
WPA1, WPB1, B2, B6 & B7
|
BT, Imperial DoC, Philips
|
Emergence of new regulatory approaches to this type of innovative medical technology
|
M
|
Inability to comply with technical standards necessary for trial approval
|
Policy
WPA4, WPC3
|
BT, Imperial BEIC
|
Changing government policy direction, refocus on different targets, reduced budgets
|
L
|
Lack of demand for telecare from health / social care stakeholders
|
Commercial
WPA1-4, WPC3
|
BT, Imperial BEIC, Philips
|
Poor end-user adoption
|
M
|
Demotivation of commercial partners
|
Technical/ Commercial
WPA4, WPC3
|
BT, Imperial BEIC
|
Poor cost-benefit outcome -
|
M
|
Small potential market for target technologies
|
Technical/ Commercial
WPA1, A2, A4, WPC3
|
BT, Imperial BEIC
|
Fragmented UK customers in health and social care (framework is fragmented and heterogeneous, and integration with legacy systems is a significant challenge) -
|
M
|
Low potential market share for target technologies
|
Trial Related
WPC1 to C3
|
BT, Imperial BEIC and DoC, Philips
|
Maintaining engagement from chosen PCT, in this case, Liverpool, due to NHS reorganisation
|
L
|
Inability of project management team to overcome barriers to uptake of trial proposal from PCT.
|
Managerial
WPM&A
|
Imperial DoC
|
Failure to manage project effectively
|
L
|
Inefficient use of resources; failure of major/critical work packages
|
Work Package
|
Responsibility
|
Risk
|
Likelihood
(L/M/H)
|
Impact
|
Technical/ Commercial
WPA1 – 4, WPB1 – 7
|
BT, Imperial DoC & BEIC, Philips
|
Inability to overcome user privacy and security issues as defined by user specification research
|
M
|
User resistance to system; ultimately, could inhibit approval for trial
|
Technical
WPA3 & WPB6
|
BT, Imperial BEIC, Philips
|
Reliability and usability -
|
M
|
User resistance to system; ultimately, could result in trial becoming unviable
|
Updated Project Issue Register
Repeat as necessary:
Issue Number:
|
Issue Type:
|
Description
|
Status:
|
|
Partner Progress Reports
Attach all partner progress reports to this report, including one from the Lead Partner.
Attach Minutes of Progress Meetings and other supporting evidence (presentations etc) as appropriate.
Monitoring Officer’s Report
Overall Assessment
Provide an assessment of the overall project achievements since the last progress report. Highlight any deviation from the Second Level Plan and provide recommendations to Contractor/DTI as necessary.
|
|
Exceptions and Issues
Recommendations
Technical Progress
Assess the progress of the technical work on a work package by work package basis.
|
|
Partners and Project Management
Assess the adequacy of the project management arrangements.
|
|
Collaboration
Assess the level of collaboration between partners and between the project and related projects and KTN activities.
|
|
Equipment and Facilities
Assess the benefit to the project of any purchases, facility rental etc
|
|
Progress against Deliverables, Milestones and Schedule
Note any variations from schedule. Identify any impact on the overall timescales and dependencies.
|
|
Project Spend Profile - See Spreadsheet Provided by Lead Partner
Assess whether the grant claim for each partner is consistent with the deliverables achieved, noting that monies must be committed and defrayed before claim.
Note any variation in the spend categories and profile and assess its likely impact.
|
|
Human Resources
Assess whether the project resources appear satisfactory and are being effectively deployed.
|
|
IPR, Beneficial Ownership, Publications and Confidentiality
Note any issues regarding IPR or beneficial ownership.
Note any issues regarding publications and confidentiality.
|
|
Dissemination
Comment on any dissemination, publication or involvement in KTN or other activities.
|
|
Exploitation Plans
Detail the progress on development of exploitation plans and assess their likely impact.
|
|
Financial Evidence
Note any concerns over the adequacy of the supporting financial evidence and make recommendations to the Contractor/DTI.
Note whether the 85% spend limit has been reached by any partner.
|
|
Problems
Summarise any concerns over the project. Assess the likely impact of these concerns and make recommendations as necessary to the Contractor/DTI for resolution of the problems.
|
|
Project Quarterly Progress Report
Template Issue 3.0
|
|
|
Share with your friends: |