1 / 8

Julian Martin Alasdair Goodfellow

Julian Martin Alasdair Goodfellow. FSA IT Overview. Current landscape Food Standards Agency is merger of two different agencies Span of control over all four United Kingdom countries Circa 100 IT systems with some data duplication

fmacon
Télécharger la présentation

Julian Martin Alasdair Goodfellow

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Julian Martin Alasdair Goodfellow

  2. FSA IT Overview • Current landscape • Food Standards Agency is merger of two different agencies • Span of control over all four United Kingdom countries • Circa 100 IT systems with some data duplication • 853/2004 Establishment data is published monthly on www.food.gov.uk as spreadsheets • FSA Technology Stack • Primarily Microsoft based architecture • SQL Database platforms for Agency wide systems • Prevalent use of localised Access and Excel solutions • Web Services, WCF and XML/XSD utilised for information interchange where viable • Future strategic plan • Rationalisation of Agency systems • Targeting a small number of re-usable platforms • All data (Inc. Establishments for TRACES) in unified RDBMS platforms

  3. Establishment Data Analysis • FSA wide analysis undertaken for 853/2004 Establishment data • RAG Status measured for: ‘Availability’, ‘Accuracy’, ‘TRACES Conformance’ and ‘Ease of Extraction’; Highlighting areas for follow up Note: Data Summary shows percentages of data sources, not establishment records

  4. Establishment Data Sources • Multiple sources exist within the Agency across the 853/2004 sections • RDBMS • Access Databases • Spreadsheets • Meat Establishments have a unified system covering multiple sections • RDBMS Platform in place - Single Information Repository (SIR) • Used as the Meat Establishment master across multiple FSA applications • TRACES data received from Local Authorities • Local Authorities inform the FSA of data changes manually • Some data shortfalls exist • Physical records kept in parallel which contain extended data • Manual processes undertaken to unify data for publication • Data from each FSA area is sent monthly as XLS for publication

  5. Single Information Repository • FSA Line of Business System for Meat Establishments • Data for sections 0-6 and 13–15 where the FSA is the Issuing Authority • SQL Server Database with .Net browser based user interfaces • High conformance with TRACES data requirements (Highlighted) Large Schema Image

  6. Summary • Web Services are already in active use within the FSA • Data could be leveraged from existing sources for submission • Data cleansing and unification will increase data value • Upcoming Strategic Platform will unify FSA data and allow automated XTB Web service interaction

  7. Traces and XTB Queries • TRACES Questions • Will all data be published? (e.g. full uploaded addresses) • Who will have access to published data? • Schema Questions • What is the definition of Business Name. • Establishments can have multiple names (License name, Trading Name, etc.) • Can CA code be included in approval number? • LA approvals are XX1234, whereas FSA are 1234, is there a specific format TRACES would prefer • Is there an EU list of all Cities that have a CITY_ID? • Can the definition of City Postal Code be expanded upon? • Postal codes can cover part of a city, or large areas outside the city boundary • Is there an EU list of all AUTHORITY_CODE values? • Or are the values here acceptable • Where Sub-Establishments exist should separate establishment records be submitted for each (e.g.; many market stalls (Cutting plants) at a single market) • Are APPROVAL_NUM and APPROVAL_NUMBER different? • Is this just a nomenclature change between entities • Given that LMS Categories are dynamic, should the FSA maintain a mapping function from local to LMS data?

  8. Any questions?

More Related