Transformations at GPO: An Update on the Government Printing Office's Future Digital System George Barnum Coalition for Networked Information December 4, 2006

1 The Fdsys Vision GPO’s Future Digital System will be a world class system for managing official Government content. The system will verify and track versions, assure authenticity, preserve content, and provide permanent public access. The system will be: –Rules based –Policy neutral –Modular and adaptable

2 FDsys overview FDsys will automate the collection and dissemination of electronic information from all three branches of government Electronic markings will indicate that the information is authentic and will identify versions of documents that have been revised Information will be permanently available in electronic format Information will be accessible for Web searching, viewing, download, and printing Document masters will also be available for conventional and on-demand printing

3 Status An RFP was issued for the Master Integrator in early April Harris Corporation was awarded the contract on August 2, 2006 Harris showed up for work on August 9, 2006 (and haven’t left so far!)

4 Harris -- Background Building large, high volume digital archives and information systems for decades Archived content includes; documents, metadata, images, census data, weather data, space data, video, and audio Runner up on the National Archives ERA program Investing in laboratories and research in digital archives, digital preservation, and search technologies Involved in the library and digital archive communities

5 Master Integrator Role Harris will design, develop, deploy and test FDsys –Collaboratively select products / technologies –Integrate COTs including developing workflows –Conduct system testing –Prepare training materials, user manuals, and conduct training Working closely with GPO and user communities –Working hand in hand with GPO on site –Including GPO Business Units in key decisions and system development –Engaging stakeholders

6 Master Integrator Methodology CMMI best practices enable organizations to –explicitly link management and engineering activities to business objectives –expand the scope of and visibility into the product lifecycle and engineering activities to ensure that the product or service meets customer expectations –incorporate lessons learned from other areas of best practice (e.g., measurement, risk management, and supplier management) –implement robust, high-maturity practices –address organizational functions critical to products and services –more fully comply with relevant ISO standards

Producer Content & Metadata Access Search Results Queries Archival Storage Ingest Data Management GPO Users Order Information Government Agencies & U.S. Congress Content & Metadata Validation Authentication, Indexing & Preservation Cataloging, Search Engine & Reference Tools GPO Users Consumer End Users Content & Metadata Results Queries Content & Metadata Storage How FDsys Works Trusted Repository

8 Content Packages The OAIS packages –Submission –Archival –Dissemination Our model also defines –Access Comprised of derivatives, intended to keep the archival and high-demand access environments segregated

METS Wrapper content Rendition 1 Digital Object A Digital Object … Digital Object B metadata Rendition 1 TechnicalAdministrativePreservation Representation Information Descriptive Rendition 2 Rendition … Content Package XML File Digital Object Folders & Files directory Key: FDsys Manages Content & Metadata

10 Program Management GPO has implemented a phases and gates approach for managing the program. Development / Design Certification Preliminary User Requirements Roll out / Beta Testing Phase 1 Concept of Operations Basic Concept/ Vision System Requirements Gate 1 Gate 2 Gate 3 Gate 4a Gate 5 Gate 6 Phase 2 Phase 3 Phase 4a Phase 5 Phase 6 Analysis/ Design Gate 4b Phase 4b Phases 4a through 6 are structured to support each Release.

11 Release 1 Timeline Development / Design Certification Roll out / Beta Testing System Requirements 10/18/06 4/10/07 5/15/07 Phase 4a Phase 5 Phase 6 Analysis/ Design 1/12/07 Phase 4b Development / Design Certification Roll out / Beta Testing System Requirements 1/17/07 7/12/07 8/31/07 Phase 4a Phase 5 Phase 6 Analysis/ Design 3/26/07 Phase 4b Release 1.B Release 1.C We are here

12 time capability Internal Pilot Release 1.B External Launch Core Functionality External Launch Core Functionality Release 1.C Enhancements Releases 2 and 3 Planned Fdsys Development Spring 2007 Autumn 2007

13 Content Submission Basic Access and Content Delivery Enhanced Capabilities time capability 1.B Final Core Functionality 1.C 2  Releases & Functionality

14 Release 1B Internal pilot release – testing in April, 2007 Ability for users to submit content and metadata Creation, collection and editing of content metadata using MODS Ability for users to access, search and request content using a Web based user interface Capability to combine content and metadata into information packages (SIP, AIP, ACP and DIP)

15 Release 1C First external release – launch in second half of 2007 Creation, collection, editing and sharing of content metadata supporting multiple standards Basic authenticity and integrity checks on submitted content submitted Verification that submitted content has not been altered and is not a duplicate Ability to assign persistent name Basic preservation processing through refreshment

16 Release 2 Enhanced functionality for search and access Enhanced functionality for content creators Preservation processes

17 Upcoming Activities Conduct Release 1B and Release 1C Trade Study Reviews resulting in the selection of key system technologies. Develop FDsys Workflows and Use Cases. Continue outreach activities with stakeholders. Develop Beta Testing Plan for participants in release 1B pilot. Beta testing is a stage of system testing involving external exposure or operation of the system.

18 Additional Information Program documentation is available on the GPO website: The FDsys Team