SOURCES SOUGHT
R -- Development and support services for GPO's GOVINFO System
- Notice Date
- 5/5/2017
- Notice Type
- Sources Sought
- NAICS
- 541512
— Computer Systems Design Services
- Contracting Office
- Government Publishing Office, Acquisition Services, Acquisition Services, 732 North Capitol Street, NW, Washington, District of Columbia, 20401
- ZIP Code
- 20401
- Solicitation Number
- GPO-GOVINFO-RFI
- Archive Date
- 6/10/2017
- Point of Contact
- Lorna E. Baptiste-Jones, , ShaMona Avery,
- E-Mail Address
-
LBaptiste-Jones@gpo.gov, savery@gpo.gov
(LBaptiste-Jones@gpo.gov, savery@gpo.gov)
- Small Business Set-Aside
- N/A
- Description
- GPO GOVINFO SOURCES SOUGHT SOURCES SOUGHT SYNOPSIS: Solicitation Number: GPO- GOVINFO -RFI Notice Type: Sources Sought Contracting Office Address: U.S. Government Publishing Office, Acquisitions Services Division 732 N. Capitol Street, NW Room A-332 Washington, D.C. 20401 Synopsis: This is not a solicitation but rather a Sources Sought Synopsis to determine potential sources for information and long-term planning purposes. 1. Purpose : The purpose of this Sources Sought is for the Government Publishing Office (GPO) to conduct market research to identify contractors that are able to provide development and support services for the GPO's govinfo System, formerly referred to as GPO's Federal Digital System (FDsys). 1.1. This Request for Information (RFI) is not a Request for Proposal (RFP). It is a market research tool (MMAR Part 10) being used to determine potential contractors capable of providing the services and solutions described herein prior to determining the method of acquisition and issuance of a RFP. It is also a tool to get feedback on the requirement which is detailed in this document. Feedback is encouraged and appreciated. 1.2 The North American Industry Classification System (NAICS) codes contemplated for this requirement are 541512 (Computer System Design Services) which has a corresponding Small Business Size Standard of $27.5M and 541511 (Custom Computer Programming Services) which has a corresponding Small Business Size Standard of $27.5M. 1.3 Responses to this RFI are not considered offers and cannot be accepted by the Government to form a binding contract. This RFI is for market research purposes only. Respondents should not submit any proprietary information when responding to this RFI. Respondents should also note that the Government will not return any information submitted in response to this RFI. The Government is not responsible for any costs incurred by respondents regarding any responses to this RFI. 1.4 Respondents must submit a capability statement that clearly define the company's ability to perform the work stated in this RFI. Interested sources who feel they possess the necessary capabilities to fulfill all or a portion of the requirement should provide the Government the following information: point of contact, address, telephone and fax numbers, email address, DUNs number, and the socio-economic category (large, small, small disadvantaged, etc.), and a summary of the company's capabilities not to exceed ten pages in length. At a minimum, capability statements should answer the following questions: •1. Do you have experience providing the solutions and services identified in this requirement? If so, please describe your experience. •2. Please provide information about your capability to fulfil all or a subset of the labor categories in this requirement. Please list each labor category and number of roles you are able to fulfill, and please address each labor category separately in your capability statement. •3. Please provide estimated labor rates for each labor category proposed to be filled. •4. Please provide any feedback or alternative approaches that should be considered by GPO. 2. Program Details : The United States Government Publishing Office (GPO) is performing market research on potential sources able to provide solutions and services for the GPO's govinfo System, formerly referred to as GPO's Federal Digital System (FDsys). Govinfo is a content management system, preservation repository, and public website that manages, preserves, and provides free online access to current and historical information from the legislative, executive, and judicial branches of the United States Federal Government today and into the future. Please refer to the System Architecture document at https://www.gpo.gov/pdfs/fdsys-info/FDsys_Architecture_NextGen.pdf for additional technical information and the govinfo about pages at https://www. govinfo.gov/about for a user-focused description of the public access website. The mission of the FDsys/ govinfo Program ("Program") is to provide the knowledge, tools, and processes to manage, preserve, and provide access to electronic Federal Government publications. The vision of the Program is to operate an efficient and effective software development program that delivers results and delights users through the use of innovative open technologies. Program values include the following: •· Agility - Rapidly and efficiently adapting to external changes. •· Flexibility - Recognizing when something is not working and adjusting to deliver results. •· Creativity - Generating original thoughts and ideas. •· Innovation - Implementing new solutions that have a positive impact. •· Collaboration - Bringing our unique knowledge, skills, and abilities together. •· Teamwork - Working together to achieve our shared goals. •· Dependability - Competently and consistently taking care of business. •· Reliability - Assisting and supporting stakeholders in their time of need. The FY15-FY17 strategic goals for the Program are as follows: •· Improve the user experience. •· Deliver results for stakeholders. •· Evaluate innovative technologies. •· Refresh or launch with shared-services or open source. •· Interface with the developer community. •· Refine our software development process. •· Provide operational support. •· Commit to preservation and assessment. •· Monitor and control costs. •· Recover costs through services to agencies. •· Communicate what we do. •· Create a sustainable staffing plan. In addition to operational support tasks, key efforts for each strategic goal are undertaken based upon identified stakeholder need and agency priority. A few examples that demonstrate the breadth of historical key efforts include developing the govinfo beta website, replacing the legacy FDsys search engine with SOLR, migrating to Jenkins, providing access to Bill Status XML Bulk Data, performing a hardware refresh at the Production and Continuity of Operations instances, providing public access to the Digitized Bound Congressional Record, performing bug fixes and enhancements, and implementing HTTPS on the public website. To implement key efforts, the Program release cycle includes four planned quarterly releases each fiscal year. Each release includes planning, development, integration, and testing activities that are performed within two week sprints in the Integration, Quality Assurance, and Stage environments followed by one week of activities to deploy to the Production and Continuity of Operations environments. Operational support tasks to monitor the system and provide corrective and adaptive maintenance are performed each day throughout the release cycle. The Program is comprised of multiple onsite, collocated teams that perform specific development and support activities, and teams generally employ either agile Scrum or Kanban practices based on the scope of work to be performed by each team. Generally and as applicable for each team, the roles of Product Owner and ScrumMaster are performed by GPO personnel and rest of the team is comprised of contracted development and support team members. GPO is seeking sources to provide development and support services and information technology (IT) solutions for the Program. Based on historical data, the following section represents GPO's initial estimate of the kinds of personnel required for successful performance of tasks by each labor category that may be called upon to provide IT solutions for the Program. In addition, GPO's best estimate for the maximum number of roles per year per labor category is indicated as a parenthetical after each labor category; depending on the needs of the Program, the minimum number of roles per year per labor category may be zero. •· Engineering Manager (Integration Manager / Agile Coach) (maximum 1) •· Build Master / Software Quality Engineer (maximum 1) •· Senior Java Engineer (maximum 8) •· Lead System Administrator (maximum 1) •· System Administrator (maximum 3) •· Network Engineer (maximum 1) •· Lead Database Engineer / Administrator (maximum 1) •· Database Engineer / Administrator (maximum 2) •· Lead Repository Engineer (maximum 1) •· Repository Engineer (maximum 3) •· Lead Search Engineer (maximum 1) •· Search Engineer (maximum 4) •· Data Analysis Engineer (maximum 1) •· Lead Web Engineer (maximum 1) •· Web Engineer (maximum 2) •· Web Front End Engineer (maximum 2) •· Web UI Design Engineer (maximum 1) •· Lead Processor Engineer (maximum 1) •· Processor Engineer (maximum 2) •· XML Transform Engineer (maximum 2) •· Business Analyst (maximum 8) •· Preservation Analyst (maximum 1) In capability statements, respondents are asked to address one or more of the labor categories (i.e. roles) above. For each labor category, vendors must be able to perform development and support tasks on-site at GPO during core business hours as defined by the Program (generally between 8am and 4pm) with optional telework and alternative work schedules at the discretion of GPO. Each role may be required to provide support outside of core business hours in order to ensure continued availability and functionality of the system. In addition, GPO is seeking input on the identified estimated labor categories and the estimated maximum number of roles per year per labor category. GPO also welcomes input on alternate approaches to providing development and support services and IT solutions for the Program. GPO recognizes that each labor category may have its own subject matter expertise and specialized responsibilities along with requirements for technological competencies, experience, and education; GPO welcomes input on these items. In general, for example, most development and support roles will have responsibilities that may include but are not limited to the following: •· Work as a member of a cross-functional team on the Program and as necessary, provide off-hours support to ensure continued availability and functionality of the system. •· Install, configure, administer, and maintain components and technologies in various govinfo environments (e.g. Production, COOP, Stage, QA, Integration). •· Support day-to-day operations by ensuring components, technologies, and related infrastructure are maintained, configured, and supported. •· Troubleshoot and resolve problems that arise with components, technologies, and the processing and publishing of content and metadata files. •· Provide technical input to stakeholders and team members to ensure new functionality and enhancements to existing functionality are built to align with GPO's govinfo architecture. •· Champion agile software development practices on cross-functional teams. •· Design, develop, document, enhance, integrate and perform bug fixes on govinfo components and technologies. •· Monitor, evaluate, recommend, and implement components, technologies, and upgrades to ensure the Program is implementing the technologies that are most appropriate and secure to carry out its mission. •· Create and maintain FDsys/ govinfo design documentation, configurations, administrative guides, and standard operating procedures. •· Work in conjunction with other FDsys/ govinfo teams to provide support for components and functionality including during system installations, patching, upgrades, testing, deployments, COOP failover/failback activities, and other activities that require cross-team collaboration. In order to aid respondents with capability statements, the following is a list of current or potential future technologies and competencies that may be required to successfully provide development and support services and IT solutions to GPO for the Program. FDsys/govinfo General Components and Technologies: •· XML, XSLT, XSL, XSD •· Custom Applications in Java EE, current supported versions and future versions •· Git, GitLab EE, GitLab/TFS Integration •· Common and standard open source software build automation tools and IDEs including Jenkins, Maven, and Eclipse •· Common open source administration automation tools •· Common open source products for analyzing data in real time •· Footprints, Trello, Jira (potential future) FDsys/govinfo General Experience: •· Experience with traditional waterfall and agile software development lifecycle frameworks including Scrum and Kanban •· Experience working on a fast-paced, high-performing agile team •· Experience authoring, editing, and maintaining design documentation •· Experience implementing solutions in a java-based environment •· Demonstrated superior oral and written communication skills •· Knowledge of FDsys/ govinfo content and architecture •· Knowledge of Federal legislative, regulatory, and judicial processes and ‎publications •· Knowledge of ISO 14721 OAIS and ISO 16363 TDR FDsys/govinfo Infrastructure Components and Technologies: •· NetApp Filers, DataONTAP, SnapMirror, Flexclone, 7-Mode, Cluster-Mode, RAID-DP •· HP Gen8 ProLiant servers, Blades, HP Insight •· Enterprise Linux, current and future versions, including security-focused versions •· OS package and license management tools •· Apache Web Server •· Oracle WebLogic Application Server current and future versions, and other open source application servers and servlet containers •· Virtualization/container tools including VMware, ESXi Hypervisor, Vsphere •· AWS or Azure Federal Cloud (possible future but will require re-architecting major components) •· ‎Hardware Load Balancer, iRules, networking, DNS, Common enterprise network hardware •· Common open source products for analyzing data in real time, Ccmmon open source monitoring tools, common open source administration automation tools, BackupPC, UptimeRobot •· Unix‎, Shell Scripts, NFS •· Load testing, Apache Jmeter •· Java HotSpot VM •· Application Performance Management (APM) such as AppDynamics or New Relic (future) •· SSL, HTTPS, standard COTS AV and AV API interface, and EV Certificates •· Account Management Tools such as Active Directory, LDAP 3 Compliant Application Directories, identity management •· FTP, SFTP, SSH •· SMTP Mail Relay •· WebDav Server •· Penetration Testing, Vulnerability Prevention, DDOS Mitigation, CIS-CAT, CloudFlare FDsys/govinfo Network Components and Technologies: •· Common enterprise network hardware •· Hardware Load Balancer •· VMware vSphere FDsys/govinfo Database Components and Technologies: •· Recent and current supported versions of Oracle Database used by Documentum including DataGuard •· MySQL used by Drupal •· Enterprise Linux, current and future versions, including security-focused versions •· Oracle Enterprise Manager, TOAD FDsys/govinfo Build, Source Code Management, and Testing Components and Technologies: •· Git, GitLab EE, GitLab/TFS Integration, common and standard open source software build automation tools and IDEs, common open source administration automation tools including Jenkins, Maven, and Eclipse •· Apache Jmeter •· Current and future supported versions of Selenium, TestingNG, JUnit •· Custom Applications in Java EE, current supported versions and future versions •· Unix‎, Shell Scripts •· Enterprise Linux, current and future versions, including security-focused versions FDsys/govinfo Repository Components and Technologies: •· Repository Components •· Documentum Content Server, Developer Studio, Administrator Licenses, Process Engine, Forms Builder, Media Workspace / Digital Asset Manager, Process Builder, Process Integrator Core, Trusted Content Services Core •· Current support versions of Documentum Content Server deployed on open source application server •· Documentum WebTop Custom Web Application deployed on WebLogic •· Documentum xPlore and Interactive Delivery Service on WebLogic •· METS, MODS, PREMIS, Droid‎, PRONOM •· XML, XSLT, XSL, XSD •· RDF, OWL, SPARQL, Apache Fuseki SPARQL Server, Jena RDF Store •· Custom Applications in Java EE, current supported versions and future versions •· Active Directory, LDAP Compliant Application Directories, identity management •· Multiple common open source application servers •· WebDav Server •· API usage including api.data.gov •· Recent and current supported versions of Oracle Database used by Documentum (including DataGuard) FDsys/govinfo Processor and Common Utility Components and Technologies: •· Processor and Common Utility Components •· XHTML, AJAX •· XML, XSLT, XSL, XSD •· Custom Applications in Java EE, current supported versions and future versions •· MODS, PREMIS •· WebTrends Analytic Server (legacy application to be retired), Piwik •· iText, ImageMagick Converter, Redact-it, Jpylyzer •· Adobe standard technology for digital signing, Experience Manager, PDF Generator, Acrobat •· USLM schema •· HSQLDB used to Manage Jobs for Content Processing Framework •· Application Performance Management such as AppDynamics or New Relic (possible future) •· Custom Web Application deployed on WebLogic •· Standard COTS AV and AV API interface FDsys/govinfo Search Components and Technologies: •· Search Components •· XML, XSLT, XSL, XSD •· Custom Applications in Java EE, current supported versions and future versions •· MODS, PREMIS •· Groovy Dynamic Language •· Custom Java Content Parsers, RegEx, Search Technologies Query Parser Language (QPL), SOLR 4 deployed on common open source application servers •· SolrCloud (possible future), ElasticSearch (possible future) •· API usage including api.data.gov FDsys/govinfo Data Analysis Components and Technologies: •· Search Components •· XML, XSLT, XSL, XSD •· RegEx, Custom Java Content Parsers, MODS •· Design Documentation FDsys/govinfo Web Components and Technologies: •· Web Components •· XHTML, AJAX •· XML, XSLT, XSL, XSD •· High Visibility, High Availability, Public Facing Web Applications using Bootstrap, Backbone.js, JQuery, JQueryMobile, JavaScript, HTML5, CSS, SASS deployed on Apache Web Server •· Custom Applications in Java EE, current supported versions and future versions •· MODS, PREMIS •· Groovy Dynamic Language •· Current and future supported versions of Struts and Spring MVC-Based Custom Web Applications deployed on WebLogic, JSP •· Custom Spring MVC-Based RESTful Web Services deployed on WebLogic •· PERL, Custom extension of mod_perl •· Current and future supported versions of Drupal deployed on Apache Web Server, PHP, Custom Drupal modules written in PHP deployed on Apache Web Server •· User Experience (UX) Design, User Interface (UI) Design •· Web metrics, analytics, Piwik •· SEO, Crawlers, Sitemaps, CloudFlare •· Accessible Standards including Sections 508 and 255, WCA, WAI-ARIA •· Active Directory, LDAP Compliant Application Directories, identity management •· Application Performance Management (APM) such as AppDynamics or New Relic (future) •· API usage including Google Maps API FDsys/govinfo Web Front End Components and Technologies: •· Web Components •· XHTML, AJAX •· HTML, CSS, SASS •· Javascript •· PHP •· XML, XSLT, XSL, XSD •· MODS, PREMIS •· Groovy Dynamic Language •· Current and future supported versions of Struts and Spring MVC-Based Custom Web Applications deployed on WebLogic, JSP •· Custom Spring MVC-Based RESTful Web Services deployed on WebLogic •· PERL, Custom extension of mod_perl •· High Visibility, High Availability, Public Facing Web Applications using Bootstrap, Backbone.js, JQuery, JQueryMobile, JavaScript, HTML5, CSS, SASS deployed on Apache Web Server •· Current and future supported versions of Drupal deployed on Apache Web Server, PHP, Custom Drupal modules written in PHP deployed on Apache Web Server •· User Experience (UX) Design, User Interface (UI) Design •· Web analytics, Piwik •· Search engine optimization tools and techniques •· Accessibility Standards including Section 508, WAI-ARIA, WCAG 2.0 •· Application Performance Management (APM) such as AppDynamics or New Relic (future) •· API usage including Google Maps API FDsys/govinfo Web UI Design Components and Technologies: •· Web Components •· User Experience (UX) Design, User Interface (UI) Design •· Graphic Design software, including Photoshop, Illustrator or equivalents •· Prototyping tools, including Photoshop, Sketch, Illustrator, OmniGraffle, InVision, UXPin, Quartz, or other visual design and wireframing tools •· HTML, CSS, SASS, including media queries •· XHTML, AJAX •· XML, XSLT, XSL, XSD •· High Visibility, High Availability, Public Facing Web Applications using Bootstrap, Backbone.js, JQuery, JQueryMobile, JavaScript, HTML5, CSS, SASS deployed on Apache Web Server •· Current and future supported versions of Drupal deployed on Apache Web Server, PHP, Custom Drupal modules written in PHP deployed on Apache Web Server, PHP templating •· Accessibility Standards including Section 508, WAI-ARIA, WCAG 2.0 FDsys/govinfo XML Transform Components and Technologies: •· XML, XSLT, XSL, XSD, USLM schema •· Custom Java Transforms FDsys/govinfo Business Analyst Technologies: •· XML, HTML, CSS •· Microsoft Office •· Adobe Acrobat FDsys/govinfo Preservation Analyst Technologies: •· XML, HTML, CSS •· Microsoft Office •· Adobe Acrobat •· METS, MODS, PREMIS, Droid‎, PRONOM In order to aid respondents with capability statements, the following section provides a brief description of the estimated labor categories. Engineering Manager (Integration Manager / Agile Coach): The Engineering Manager is a multifaceted role that combines the strengths and responsibilities of a traditional Engineering Manager with those of an Integration Manager and a modern Agile Coach. The vision of the Program is to operate an efficient and effective software development program that delivers results and delights users through the use of innovative open technologies; the Engineering Manager is the champion of this vision. As an Agile Coach, this role will work with the Program teams to continuously improve and promote agile practices. As the Engineering Manager, this role is responsible for overseeing FDsys/ govinfo development and support activities by assisting GPO staff members in conveying priorities to the development teams and ensuring sound engineering practices are followed throughout the software development lifecycle. As the Integration Manager, this role will mediate and resolve any technical issues or considerations that arise among the development teams. Buildmaster / Software Quality Engineer: The dual role of Build Master and Software Quality Engineer is a technical role that is focused on influencing, shaping, and managing the software build process including builds and deployments in the Integration, QA, Stage, Production, and COOP environments, as well as developing and enhancing an automated test framework and creating automated test cases to support development across all components. The Build Master also provides oversight and resolution for GIT source code management (SCM) processes including branching, merges, merge requests, and merge conflicts. Senior Java Engineer: The role of a Senior Java Engineer is a generalist who, based on the needs of the Program, may be asked to develop and support the custom code, open source technologies, and commercial off the shelf (COTS) products that comprise all aspects of the system including the content management system, preservation repository, public website. The Senior Java Engineer needs to have in-depth knowledge of FDsys/ govinfo architecture, components, and technologies in order to sustain the system and provide technical continuity across component and cross-functional teams. System Administrators: System Administrators are primarily responsible for hardware, application, and system administration support for all instances of FDsys/ govinfo. This involves working as a member of the Infrastructure Team or other cross-functional teams as needed to support the FDsys/ govinfo Program, and as necessary, provide off-hours support to ensure continued availability and functionality of the system. System administrators serve as the Enterprise Linux Subject Matter experts, providing guidance and support to the various Program teams to meet the needs of the Program. System Administrators serve in key integration roles within the program, interacting with GPO Network, Information Security, and Enterprise Storage/Datacenter Administrators. They support the underlying architecture that supports the program through the management of hardware, storage, operating system, and network components. Network Engineer: The Network Engineer will work closely with the GPO IT Network and Telecommunications group to ensure that the supporting network infrastructure is functional and performing at the expected level to support all FDsys/ govinfo functionality. This includes but is not limited to the development and setup of new environments to support FDsys/ govinfo, including the proposal, change control, and implementation required for Access Control Lists (ACLs). Following IT Network best practices is critical to maintaining infrastructure homogeny while developing and maintaining network components required for continued access and support. Monitoring and investigating network issues in conjunction with application subject matter experts and system administrators is also critical to new development efforts and existing performance expectations or new issues that arise. Performance and security are important efforts and must continue to be monitored and researched given changing situations and priorities, and coordination and communication are pivotal to the continued success of FDsys/ govinfo. Database Engineer / Administrator: The FDsys/ govinfo Documentum repository operates on an Oracle database. The database schemas are defined and tables populated by Documentum applications. The database maintenance is therefore not about managing schemas, tables, et cetera, unlike standalone or custom database applications. For FDsys/ govinfo, the database maintenance has to be performed in the context of the Documentum repository. Thorough understanding of the interactions between Documentum applications with the underlying database is critical to manage the database properly and effectively. Repository performance issues may find root causes in the underlying database, and proactive monitoring and careful tuning of the database is the key to maintain a healthy repository. Likewise, the FDsys/ govinfo Drupal CMS operates on a MySQL database and requires similar considerations. Database availability and uptime is also a key consideration; clustered operation and synchronization between nodes/sites is critical to daily operations, and knowledge of Oracle-specific hardware and software constraints and setup are necessary for continued service availability. Repository Engineer: The role of Repository Engineer is the subject matter expert (SME) primarily responsible for the development and support of the custom code and commercial off the shelf (COTS) products that comprise the content management system and preservation repository. Currently, the primary COTS product for the content management system and preservation repository is EMC Documentum. The Repository Engineer is also responsible for developing the govinfo Publication Linking functionality which is comprised of RDF, OWL, SPARQL, Apache Fuseki SPARQL Server, and a Jena RDF Store. Processor Engineer: The role of Processor Engineer is the subject matter expert (SME) primarily responsible for the development and support of the custom code, open-source, and commercial off the shelf (COTS) products that comprise the FDsys/ govinfo processor and common utilities including schema and transforms, analytics, content processing framework (CPF), XML Metadata Editor (XME), standard COTS AV and AV API interface, and content source module. FDsys/ govinfo content packages require extensive file processing. Generally, the processor performs tasks on content and metadata files including parsing files to extract metadata, splitting files, concatenating files, applying digital signatures PDF files, optimizing PDF files for online display, and performing schema validation. A clustered processor architecture has been implemented to meet the needs of FDsys/ govinfo. Characteristics of the processor architecture include a cluster of processors, parallel processing, distributable, highly configurable, plug and play capability, and loosely-coupled interaction with the repository. Currently, the primary COTS and open-source products for the processor and common utilities include Piwik, WebTrends, standard COTS AV and AV API interface, ImageMagick, Jpylyzer, iText, Redact-it, Adobe standard technology for digital signing, and Adobe Acrobat. The java-based custom code includes an XML metadata editor (XME) that utilizes the Orbeon XFORM server, a content processing framework, parsers and authority files, and the processor including FDsys/ govinfo XML schemas and transforms. The Processor Engineer must also have strong troubleshooting skills to be able to quickly resolve issues with packages that fail processing. Search Engineer: The Search Engineer is the subject matter expert (SME) primarily responsible for the development and support of the custom code and open-source products that comprise the search engine, content parsers, and public website. Currently, the primary open-source product for the search engine is SOLR. The XML and java-based custom code includes content parsers, query processor language, publisher, consistency check, APIs, transforms, and configuration files along with utilities for monitoring and reporting search functionality, performance, and status. Search Engineers play a key role in the ingest of content into the system; consequently, Search Engineers must also have strong troubleshooting skills to be able to quickly resolve issues with packages that fail parsing and publishing, in coordination with the Processor and Repository Engineers. Data Analysis Engineer: The Data Analysis Engineer performs both technical and analytical tasks to support the addition of new content and collections into FDsys/ govinfo. This role is primarily responsible for creating and updating the Data Management Definition (DMD) documents that describe how content and metadata for each collection is generated, processed, managed, and utilized by system components. In addition, the Data Analysis Engineer will frequently meet with internal and external stakeholders to discuss needs and propose solutions so they must have working knowledge of both the system and the content that is in scope for ingest into the system. The Data Analysis Engineer is also responsible for developing, utilizing, and maintaining any scripts, processes, or documentation necessary to prepare content and metadata for submission into GPO's Open Archival Information System (OAIS) compliant (ISO 14721) system. Web Engineer: The Web Engineer is the subject matter expert (SME) primarily responsible for the development and support of the custom code and open-source products that comprise the FDsys/ govinfo public websites, mobile sites, bulk data site, sitemaps, public API, content delivery module, web services, transforms, configurations, and related infrastructure such as the Apache web server and WebLogic application server. Currently, the primary open-source web content management system for the govinfo public website is Drupal. The XML and java-based custom code includes the FDsys search web application including bulk data, preview, static pages, committee pages, and transforms; the GPO web application including the preview context, bids, and static pages; the content delivery module; sitemaps; mobile application user interface; mobile web services; GPO web services; public search API; and govinfo web services. The Web Engineer is also responsible for the development and support of the current GPO.gov website in the FDsys environment until the new GPO.gov 2.0 site is out of Beta and the current site is retired. Note: The new GPO.gov 2.0 site is outside of the scope of this requirement, and is managed by a separate team within GPO in a separate environment. Web Front End Engineer: The Web Front End Engineer is primarily responsible for interacting with backend web services to implement user-facing features, with an emphasis on performance and scalability. The Web Front End Engineer will primarily work with the Web UI Design Engineer and Web Engineers, and other team members as necessary to implement functionality for the FDsys/ govinfo public user interfaces. Web UI Design Engineer: The Web UI Design Engineer is primarily responsible for designing the Web user interface for govinfo, by maintaining and extending the existing style in coordination with the other Web Engineers. The Design Engineer collaborates with product owners, ScrumMaster, and developers to define and implement innovative solutions for product direction, visuals, and the user experience, including executing all visual design stages from concept to final hand-off to engineering and developing original ideas that bring simplicity and user friendliness to complex design roadblocks. The Web UI Design Engineer also serves as the Program subject matter expert for accessibility. XML Transform Engineer: The role of the XML Transform Engineer is to serve as the subject matter expert (SME) primarily responsible for transforming, in a manual, semi-automate, and automated means, file formats such as text, locator-coded text, HTML, SGML, or XML into USLM XML or other schema as required by GPO. Business Analyst: The Business Analyst role provides support to GPO staff members on the Program who serve in various roles based on the needs of the Program including but not limited to the Program Manager, Deputy Program Manager, Release Manager, Epic Owners, Product Owners, Preservation Manager, Test Manager, Testers, Risk Manager, Infrastructure Manager, Quality Assurance / Customer Support / Operational Support Manager, Customer Engagement / Account Manager, and Communication / Social Media / Content Curation Manager. The Business Analyst may be asked to support one or more of these Program roles based on the evolving needs of the Program. Preservation Analyst: The Preservation Analyst must have knowledge of and experience with ISO 16363 Audit and Certification of Trustworthy Digital Repositories standard and related standards, the Federal Digital System FDsys/ govinfo, and GPO's preservation initiatives in order assist GPO as it embarks upon an ISO 16363 audit of FDsys/ govinfo by an accredited outside organization. The Preservation Analyst will support the Program Manager and other GPO Program staff by developing, evaluating, and monitoring preservation strategies, plans, and practices to ensure the integrity of the repository. The Preservation Analyst role will assist with GPO's initiative to seek and maintain certification of FDsys/ govinfo under the ISO 16363 standard and perform related duties in support of this initiative. 3. Contacts: All responses, questions, or comments must be submitted to the identified GPO Point of Contact by 2:00pm(eastern standard time) May 26, 2017 ; via EMAIL only please. Email: AcquisitionServicesproposals@gpo.gov (Please reference "GPO- GOVINFO -RFI" in the subject line, when responding). No phone calls please. GPO Point of Contact: Lorna Baptiste-Jones, Contracting Officer Address: U.S. Government Printing Office, Acquisition Services Division, 732 North Capitol Street, NW, Room A332, Washington, DC 20401
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/GPO/PSPSD/WashingtonDC/GPO-GOVINFO-RFI/listing.html)
- Record
- SN04497838-W 20170507/170505234402-bd6675ea65c5855cb87863ca9ecf67c7 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |