ID15170007_IAE_PA&G_PWS_DRAFT_2017-04-20.doc

Solicitation # 5TP57100245 IAE Program Assurance and Governance ITSS Solicitation #: ID15170007

DRAFT

PERFORMANCE WORK STATEMENT

For

Program Assurance and Governance A procurement by the

U.S. General Services Administration on behalf of

Office of Systems Management (QD) Integrated Award Environment (IAE)/System for Award Management (SAM) Washington, D.C.

Solicitation Number ID15170007 Contract Number TBD This requirement is being solicited as a Task Order under the NAICS 541519 – Other Computer Related Services Product Service Code D399 – IT and Telecom – Other IT and Telecommunications

Contents

51 Background:

5Integrated Award Environment (IAE)/System for Award Management (SAM)

5Organizational Mission

5Procurement Objective

5IAE/SAM Program History

6IAE/SAM Current Status

72 Orientation

7General Scope of Work

7Resources

7Placement and Management of Work

8Customers

8Performance Monitoring

8General Definitions

9Technical Definitions

93 Assumptions

94 Primary Performance Objectives (Technical)

10Objective 1 – Program Assurance and Release Planning

10Sub-objective 1.1 Product Assurance Support

11Sub-objective 1.2 Release Planning Support in Scaled Agile Framework (SAFe)

12Objective 2 – Enterprise Architecture Support

12Sub-objective 2.1 Enterprise System Architecture Support

13Sub-objective 2.2 Data Architecture and Management Support

15Sub-objective 2.3 User Interface and User Experience Support

16Objective 3 – Technical Governance and Requirement Support

17Sub-objective 3.1 Technical Governance Support

18Sub-objective 3.2 Technical Requirements Support

195 Meeting Objectives

19Meeting Objective 1 – Initial Business/Kickoff Meeting

20Meeting Objective 2 – Ad hoc Technical / Work Status / Administrative Meetings

20Meeting Objective 3 – Contract Administration Meetings

206 Contract-wide Objectives

20Contract-wide Objective 1 – Contract and Project Management

20Contract-wide Objective 2 – Subcontract Management

20Contract-wide Objective 3 – Business Relations

21Contract-wide Objective 4 – Contractor Response

21Contract-wide Objective 6 – Team Continuity and Employee Retention

21Contract-wide Objective 7 – Professional Appearance

217 Additional Performance Requirements

21Location of Work

22Time of Work

22Normal Hours

22Holidays

22Government Facility Closures

23Performance at the Contractor’s Facilities

23Travel

23Limitations on Contractor Performance

23Privacy Act Requirements

23Personal Services

24Rehabilitation Act Compliance (Section 508)

25Avoidance and/or Mitigation of Actual or Potential Organizational Conflicts of Interest

258 Personnel Requirements

25Personnel Qualifications – General

26Key Personnel Definition and List

26Key Personnel Qualifications

26PROJECT MANAGER

27DELIVERY LEAD

27RELEASE TRAIN ENGINEER

28ENTERPRISE ARCHITECT

28FRONT END ARCHITECT

29TECHNICAL GOVERNANCE LEAD

30Key Personnel Substitution

31Non-Key Personnel – Additional Qualifications

31Non-Key Personnel Substitutions

31Staff Maintenance

32Contractor Employee Work Credentials.

329 Security Requirements

32Compliance with Security Requirements

32Employee Security Requirements

32Common Access Card & ID Badges

32Facility Security Requirements

32OPSEC Requirements

33Personal Identity Verification

33Unescorted Entry Authorization Certificate

33Non-Disclosure Statement.

3310 Period of Performance

3411 Deliverables

34Items, Time of Delivery, Place of Delivery

36Data Requirements / Descriptions

36Contractor Employee Non-Disclosure Agreement.

36Quality Control Plan.

36Staff Matrix.

37Funds and Man-Hour Expenditure Report

37Monthly Status Report (MSR)

37Trip Reports IF REQUIRED

38Other Reports

3812 Quality Assurance and Quality Control

38Contractor Quality Control Plan (QCP)

39Government Quality Assurance Surveillance Plan (QASP)

3913 Government Furnished Items [USE AS NEEDED]

39Data

39Equipment – Tools - Accessories

40Materials

40Facilities

41Safeguarding Government Furnished Property - Physical Security

41Training

41Government-Furnish Services

4114 Government Delays in Reviewing Deliverables or Furnishing Items

4215 Notices

42Contracting Officer’s Technical Representative

42Government Technical Representative - Task Management

4216 Contact Information

42Contractor Contacts

42Government Contacts

4317 Additional Provisions

43Data Rights

43Limited Use of Data

43Proprietary Data

43Inspection and Acceptance

44Contract Type

44Ceiling Price Notification

44Task Order Funding

44Incremental Funding

44Material and Material Handling Costs

45Productive Direct Labor Hours

45Invoicing and Payment

45Payment for Unauthorized Work

45Payment for Correction of Defects

45Attachments

451 Business Epics

452 Detailed Program Roadmap

453 Agile Playbook

454 Current IAE Tool List/software

455 BSP Information sheet

456 Programming Languages needed (referenced on page 12)

457 QASP (Quality Assurance Surveillance Plan)

458 Organizational Conflict of Interest Provisions

1 Background:

Integrated Award Environment (IAE)/System for Award Management (SAM) Organizational Mission

The mission of the GSA Office of Integrated Award Environment (IAE) is to support a common, secure business environment which facilitates and supports cost-effective acquisition of, and payment for, goods and services; effective management of federal acquisition and assistance awards; and consistent transparency into federal acquisition and assistance awards.

The IAE vision is to continue to evolve and integrate the existing shared portfolio of ten (10) electronic systems used for awarding and administering federal financial assistance (i.e., grants, loans) and contracts through Agile Scaled Agile Framework (SAFe) Development Processes on the Common Services Platform (CSP) and in the future, the Business Services Platform (BSP).

The largest and most complex of the e-Government initiatives, the IAE works on behalf of the acquisition and financial assistance communities to save money, be more efficient, reduce burdens on the communities we serve, and improve federal award management.

Procurement Objective

The purpose of this procurement is to obtain the necessary contractor support in the areas of (1) program assurance and governance, (2) Scaled Agile Framework (SAFe) release planning, (3) enterprise architecture, (4) data management, (5) product delivery, and (6) product development to operations and maintenance transition, to enable the GSA Office of Integrated Award Environment to fulfill its SAM modernization mission.

This effort will require the contractor to collaborate with the Government and other contractor teams to provide support on Program Assurance, Enterprise Architecture including Data Architecture & User Interface design and Technical Governance. This support shall provide sustainability of deliverables and prepare a smooth transition to the operations and maintenance phase of the new SAM.gov (referred to as beta.sam.gov throughout modernization activities). Currently, the program is operating with a focus on nine (9) Business Epics (Attachment 01) for shared functionality across the systems, which will require the vendor to collaboration and function with multiple vendor and Government teams.

IAE/SAM Program History In 2002, Integrated Acquisition Environment was created as an e-Government (e-Gov) initiative under the President’s Management Agenda. As part of the e-Gov initiative, the Office of Management and Budget (OMB) designated GSA as the executive agent of the Integrated Acquisition Environment. In 2013, the Integrated Acquisition Environment was renamed the Integrated Award Environment (IAE) by its governance to reflect its management of procurement, grants, and federal assistance data. In 2017, the organization shall be renamed The Office of Systems Management (QD), IAE/SAM.

The concept behind the IAE/SAM is to provide Federal Government agencies and contractors with a shared IT system to manage the acquisition and grants-making process from solicitation through closeout. The Goals of the IAE/SAM Program are to (1) create a simpler, common, integrated Information Technology (IT) service that promotes competition, transparency, and integrity; (2) increase data sharing across the Government and with the public to enable better decisions in procurement, logistics, payment, and performance assessment; and (3) take a unified approach to obtaining modern tools to leverage investment costs across the Federal Government for award-related IT services.

The IAE/SAM enables all phases of the Federal awards management lifecycle, manages the common source of entity information for acquisition and financial assistance (grants and loans) communities, provide a market research source for contract administration to the Federal acquisition community as well as private and commercial firms that are interested in doing business with the Government, and stores information that the public in general seeks on how tax dollars are being spent. Provide subcontract reporting opportunities for Agency and Contractor communities. IAE provides data for Government and non-Government stakeholders including the general public.

IAE awarded a task order to provide a common technology platform (referred to as the Common Services Platform) that will facilitate the functional sharing of “core” acquisition and financial assistance processes. The Common Services Contractor will provide common, shareable services to accommodate the insertion of “core” processes into the platform framework on an iterative basis. The IAE/SAM will be moving to the Business Services Platform in 2017.

IAE/SAM is governed by the Award Committee for eGov (ACE) structure which includes the Procurement Committee for eGov (PCE) and the Financial Assistance Committee for eGov (FACE). Additionally, all IAE operations are coordinated and prioritized through the Configuration Control Board (CCB) that consists of representatives from each of the 24 Chief Financial Officer (CFO) agencies. These same agencies contribute funding for the IAE operations.

IAE/SAM Current Status

IAE currently sees over $1 trillion and 3.3 million transactions in federal assistance and procurement awards across all the IAE systems. With growing numbers, IAE currently has over 3.4 million registered users and over 500 million hits or page views per month.

The current IAE systems were developed over several years as free-standing, web-based systems to fulfill different roles throughout the acquisition and grants-making process. Many are operated and maintained by independent contractors. Shared functional components of the application stack for these systems are limited to co-location services that cover some systems and a consolidated end-user help desk that supports a different subset of the systems.

Current IAE systems consist of the following:

1.

System for Award Management (SAM)

2.

Federal Procurement Data System – Next Generation (FPDS-NG)

3.

Federal Business Opportunities (FBO)

4.

Electronic Subcontracting Reporting System (eSRS)

5.

Federal Funding Accountability and Transparency Act (FFATA) Subaward Reporting System (FSRS)

6.

Contractor Performance Assessment Reporting System (CPARS)

7.

Federal Awardee Performance and Integrity Information System (FAPIIS)

8.

Past Performance Information Retrieval System (PPIRS)

9.

Wage Determination OnLine (WDOL)

10.

Catalog of Federal Domestic Assistance (CFDA)

Currently, the IAE systems are self-contained in silos and run in differing environments; and as a result, resources are not used efficiently in sharing capabilities and data across the ten IAE systems. Furthermore, the implementation of the IAE systems is inflexible both in its software and infrastructure configuration.

2 Orientation General Scope of Work This Performance Work Statement (PWS) defines program support objectives for implementation of new SAM.gov web portal.

This task order will be placed under the 8(a) STARS II or Federal Supply Schedule 70 contract. It is anticipated that work will be performed using a Fixed Price and/or Labor Hour or Time and Material price structure.

Work will be performed over the period of approximately five years, with an anticipated Base Period of 12 months and four Option Periods of 12 months each.

Resources

Under this contract/task order, unless otherwise stipulated (see Section 13 – Government Furnished Items), the Contractor shall furnish or provide all personnel, personnel management and supervision, all related internal supporting business functions (including background and “overhead” personnel), materials, supplies, equipment, and facilities to perform the full range of technical and administrative services required by this contract/task order.

During the course of this contract/task order, the Government may make additional Government Furnished Items (GFIs) -- materials, equipment, and facilities -- available upon receipt of a written request from the Contractor to the Government Technical Representative. These GFIs, if provided, would be in addition to those initially set forth in Section 13.

The contractor shall provide fully trained personnel. (Reference “Staff Employee Requirement” in Section 7 of this PWS.)

Government personnel will be made available to provide technical input, answer questions, review completed draft deliverables, provide feedback, and provide shipping directions for deliverables.

Placement and Management of Work

All work under this Task Order is either specifically described in this PWS or shall be assigned to the Contractor in writing by the Contracting Officer’s Representative (COR) using a Technical Directive form. Contractor employees shall perform work as specified in this task order as directed by the Contractor’s designated project manager, who shall have full responsibility for the assignment and monitoring of Contractor employee activities. All work shall be performed within the scope of this PWS and the Government will not ask or require the Contractor to perform work that is outside of the scope of this task order.

Customers

The customer and recipient of all work performed under this contract order is the Office of Systems Management (QD), IAE/SAM located at 1800 F Street NW HUB 4323 Washington, DC 20405.

Performance Monitoring

Contractor performance shall be monitored by the Government representatives in accordance with the Contractor’s Quality Control Plan (QCP) and the Government’s Quality Assurance Surveillance Plan (QASP)(see Section 12, below).

General Definitions BSP – GSA Business Services Platform – The next generation IT platform for hosting multiple Government–wide acquisition applications.

CO – Government Contracting Officer (also PCO – Procuring Contracting Officer) COR – Contracting Officer’s Representative (See Section 15, below) FTE – Full Time Equivalent, the number of labor hours equal to those that would be worked by one employee in a year. For this procurement action 1960 hours is considered an FTE.

CPARS – Contractor Performance Assessment Reporting System – This is a system that generates reports that are created by the government evaluators to document contractor performance.

CSP – Common Services Platform – A single IT platform for hosting multiple Government–wide acquisition applications.

IAE – GSA Office of Integrated Award Environment

IAE PMO – GSA Integrated Award Environment Project Management Office

Normal Workweek - A workweek is 40 hours.

Overtime - Time worked by a contractor’s employee in excess of the employee’s normal workweek. (Note: Premium pay is not authorized under this task order for overtime work.)

Quality Assurance - A planned and systematic pattern of all actions necessary to provide confidence to the government that adequate technical requirements are established; products and services conform to established technical requirements; and satisfactory performance is achieved.

Quality Assurance Personnel (QAP) - A functionally qualified government person(s) responsible for surveillance of contractor performance and providing communications to the contractor(s) and PCO.

Quality Assurance Surveillance Plan (QASP) - A plan detailing the contract surveillance procedures and containing the Objectives, Measures and Expectations that will be used to evaluate contractor performance of the PWS objectives.

Quality Control - Those actions taken by a contractor to control the production of outputs to ensure that they conform to the contract requirements.

TO – Task Order

Technical Definitions None

3 Assumptions

The contractor shall employ a staff with sufficient experience and expertise to perform each of the tasks in this PWS.

4 Primary Performance Objectives (Technical)

The overall objective of this Task Order is for the Contractor to provide program support to insure that the new SAM.gov (beta.sam.gov) delivery and upcoming operations and maintenance (O&M) are achieved. This is to be done by collaborating with the Government and other contractor teams through Program Assurance and Agile Scaled Agile Framework (SAFe) Release Planning support, combined with the requirements for Enterprise Architecture, Data Management support and Governance Support. This support will focus around the nine (9) Business Epics (Attachment 01) as presented to support the IAE defined goal of SAM.gov as a single system. There is no intention that performance of this task order will replace the development work provided by other contractors who are working on this project. All deliverables and work products provided to the Government under this Task Order will become the property of the Government; therefore, they shall be delivered in a format that will allow the Government to edit them after the conclusion of this Task Order.

In summary, the overarching objectives of this requirement are as follows:

Business Objectives

· Support the Government who is leading the overall planning, building, testing and deployment effort. Enforce the use of the Scaled Agile Framework (or SAFe) process and manage the dependencies and risks.

· Provide analysis and forecasts to update the Program Detailed Roadmap (Attachment 02) with the proper adjustments during the modernization period.

Technical Objectives

· Provide technical support for the following.

· Completion and Maintenance of the beta.sam.gov architecture

· Support for data architecture & management

· Support for user interface & user experience design

· Support for technical governance.

· Ensure that the IAE system modernization adheres to the Program Detailed Roadmap (Attachment 02)

· Assist the Government with preparation for a smooth transition to O&M.

Objective 1 – Program Assurance and Release Planning

The contractor shall meet this objective by supporting the Government in delivering a modernized SAM.gov. This shall be accomplished by collaborating with the IAE PMO, GSA IT, and other contractor teams and providing Program Assurance Support and SAFe Release Planning support as defined in the following sub-objectives. This support shall include the proper documentation of project activities (as noted below), submission of assigned deliverables, and participation in all required Agile ceremonies in support of the beta.sam.gov. These activities shall support IAE’s defined goal of implementing SAM.gov as a single system and ensuring that the modified Scaled Agile Framework (SAFe) is used to conduct program execution.

Sub-objective 1.1 Product Assurance Support

The contractor shall provide Product Assurance and Delivery Support to the IAE system modernization (beta.sam.gov). The Delivery Lead shall work collaboratively with the Release Train Engineer (RTE), which shall be provided in this Task Order, and assigned Agile Coach(es) in supporting the Government who are leading the overall planning, building, testing and deployment effort. The contractor shall collaborate with the Government in assessing the backlog and scope of releases based on business requirements, enterprise architecture, dependencies and risks. The contractor shall consolidate information and provide recommendations to the Government by tracking delivered Features and Epics in releases across Epic teams, contained within a Weekly Profile Management Report. The Government will release integrated functionalities from Business Epics based on the Detailed Program Roadmap (Attachment 02). The contractor is required to support the deliverables and work with Government for recommendations.

The contractor shall support the IAE Leadership and Management to ensure that the stated deliverables of IAE modernization program are delivered in accordance with the Detailed Program Roadmap (Attachment 02). (It is anticipated that a Delivery Lead will provide this support.) The Delivery Lead shall work closely with the team and the lead Agile Coach and Release Train Engineer (RTE) to track and measure the performance of the program execution in SAFe, identify any potential deliverable risks associated with the project and bring them to the Government’s attention with a recommended mitigation plan.

The Delivery Lead shall participate in all aspects of the new SAM.gov (beta.sam.gov) product development. This will include attending Scrum of Scrum meetings, demo meetings, release planning meetings, and any other meetings as deemed necessary by the Government.

The Delivery Lead shall work closely with the lead Agile Coach and Release Train Engineer (RTE) to support the Government and Epic teams on updates and prioritizing the overall product backlog, as required. The Delivery Lead shall also work with RTE to lead the discovery and collection of each release objectives which will support the Government’s release schedule.

The contractor shall support the Internal Change Control Board (ICCB) by assisting with the prioritization of functions, preparing features for releases, and ensuring that functionality is consistent with the IAE architecture.

The contractor shall deliver an update to the Detailed Program Roadmap in a format that will be editable by the Government. As part of this requirement, the contractor shall ensure that all information regarding key data points is current and presented in the Detailed Program Roadmap. Key data points include, but are not limited to: Feature and Product information (as pulled from JIRA and Confluence), milestones, recommendation for de-commission dates for Legacy systems, IAE Releases, functionality to be released into production, etc. The information contained in the Program Detailed Roadmap will be updated as required by the contractor, but formally delivered quarterly.

Sub-objective 1.2 Release Planning Support in Scaled Agile Framework (SAFe)

The contractor shall support the SAFe ceremonies and activities required to achieve the beta.sam.gov production goals. (It is anticipated that a Release Train Engineer and other appropriate contractor personnel will support this effort.) Release Planning and System complexity require more controls to keep the production train, composed of multiple vendor teams, on the track to ensure that the stated features and functionalities are completed. (The employment of a Release Train Engineer (RTE) is one of the techniques the Scaled Agile Framework (SAFe) Enterprise uses to keep the SAFe execution on track.) The contractor shall work closely with the Epic owners and Epic scrum masters for feature backlog, sprint backlog and release planning. The contractor shall collaborate with the IAE Agile Coach(es) to provide adequate Agile guidance and support to the Epic teams and to provide and maintain an IAE Release Plan to include the following artifacts:

Release status, including Release burndown charts

Product Backlog with priority indicators

Scrum Task boards

Release retrospective documentation

Potentially Shippable Increment (PSI) Objectives

The RTE role, as provided by the contractor, shall lead the SAFe professionals to support Government and the contractor Delivery Lead to assure the program deliverables are met on schedule as communicated through the Detailed Program Roadmap. The contractor shall:

Collaborate and provide guidance to the release train teams and participants. While the Agile Release Train (ART) and the teams that are part of the train are predominantly self-managing and self-organizing, the RTE provides guidance to help teams adapt to the environment.

Organize and facilitate the Release Planning ceremony. The organization includes, but is not limited to:

Working with necessary Government personnel to secure the ceremony site at an off-site location

Organizing the formal invite to ensure inclusion of all necessary personnel

Preparation of the agenda

Collaboration with all necessary Government and Contractor personnel prior to the ceremony to ensure proper presentations are prepared

Preparation of all instructions, rules of the ceremony and items needed for breakout sessions are ready and onsite

Facilitation of all aspects of the ceremony activities

Track and report the ART performance. The RTE focuses on facilitating ART and assist the Program Management Office which owns standard administration tasks.

Lead and facilitate the Scrum of Scrums (SoS) ceremony

Own the identified external dependencies during the two day planning meeting. This ownership includes working closely with point of contacts assigned to the external dependencies and facilitates intergroup communication and dependency resolution.

Resolve and/or escalate impediments to IAE Leadership and Management as required. Scrum masters are required facilitate the resolution of impediments within their span of influence. Once an impediment is outside of a scrum master’s span of influence, the RTE shall collaborate with the proper point of contact to resolve or escalate the impediment

Facilitate process improvement at the ART level. While teams pursue improvements based on retrospectives, the RTE facilitates ensuring the overall processes are continually being refined. Such process improvement can include the facilitation of recommendations as presented at Retrospective ceremonies.

Objective 2 – Enterprise Architecture Support

To meet this objective the contractor shall support the Government in delivering SAM.gov (beta.sam.gov) Enterprise Architecture by collaborating with the all necessary Government personnel and other contractor personnel as directed by the Government. The support shall be fulfilled by 3 Sub-objectives:

1.

Enterprise System Architecture support

2.

Data Architecture and Management Support

3.

User Interface and User Experience Support Sub-objective 2.1 Enterprise System Architecture Support

The contractor shall update and support the Government in implementing IAE SAM.gov Enterprise Architecture and Integration Management plan. The Enterprise Architecture and Integration Management plan shall document the beta.sam.gov architecture baseline, the beta.sam.gov target architecture, the tasks required to manage the beta.same.gov enterprise architecture, and the Transition Plan to the target architecture, which shall include necessary Security requirements to achieve the stated target architecture. The plan shall incorporate the necessary aspects the Detailed Program Roadmap, which will include the integration of common components, business functions through the common services and the transition of those same functions from their legacy systems. The priority of those changes to IAE will be driven by the Government and the governance bodies of IAE as identified by the Government. The plan shall be updated quarterly.

The contractor shall collaborate with Product Owners, as needed, and the Epic team architects to collect the Epic level architecture information. The Senior Enterprise Architect shall be responsible for collaboration with the Government Enterprise Architect to complete the SAM.gov architecture initial implementation (baseline) and system/components integration. This implementation should be achieved by referencing the Epic architecture info from the Epic teams. The transition to the target architectures shall be detailed in Transition Plan as contained within the Enterprise Architecture and Integration Management Plan.

The contractor shall schedule and facilitate weekly architecture status meetings with the IAE Architecture Management Team. Topics of architecture status meetings shall include, but are not limited to: technical roadmap, data architecture, GUI architecture, release planning, and IAE business priorities. The contractor shall be responsible for documenting all meeting minutes, actionable items and outcomes of the weekly Architecture meetings. Information, outcomes, and action items should be summarized within the Monthly Status Reports as provided to the Contracting Officer Representative (COR) and Contracting Officer (CO). The contractor shall document status on the progress of outstanding architectural deliverables, which shall be posted in Confluence.

The contractor shall support the planning, development and evolution of the IAE SAM.gov architecture using the Government-provided architecture tools appropriate to capture a conceptual, logical and physical architecture.

In support of planning the architecture and integration, the Government will provide information about current IAE operations and configuration. As new business requirements or operational issues arise, the vendor shall provide appropriate updates to the architecture to accommodate those changes. As a part of the IAE architecture and integration plan, the contractor shall develop as needed and maintain the following artifacts:

Architectural life cycle documentation including baseline, transition, and target architectures

Architectural technical roadmap for SAM.gov to align with IAE Release Schedule

Architectural change management plan

Methodology for architectural interrogation (Architectural Change Analysis)

(it is duplicated)

Post architectural implementation review documentation

Sub-objective 2.2 Data Architecture and Management Support

The contractor shall support the Government in the reconciliation of data elements across the legacy IAE systems into the new common services data architecture. To support this effort, the contractor shall develop the Enterprise Data Architecture. The contractor shall document all facets of data standards and develop the Master Data Management (MDM) and Governance plan and support the Government in the implementation and management of the plan across the SAM.gov product. The contractor shall use the government provided tool(s) (Attachment 04) to create, view/manage data models and produce documentation and artifacts. The contractor shall support the Government with implementation, management and governance of the plans and procedures to ensure IAE data is managed according to Federal Government and GSA policies. The plan shall be reviewed and updated Quarterly - at minimum. Adhoc changes can be made as needed.

The contractor shall coordinate with Government personnel to perform quality assurance on the data, manage changes to the metadata including impact on both development and operations, and provide analysis of existing data in support of data quality management. As a part of the Data Management and Governance Plan, the contractor shall collect, build and maintain the following artifacts:

Data Models

Enterprise Data Model (Conceptual)

Logical Data Model (if needed)

Physical Data Model (current and target)

Enterprise Data Dictionary

Defines data domains, objects, elements, business definitions, technical constraints, logical data connections and translations, data types, domain values, security controls and constraints and authoritative sources Make the Data Dictionaries available for the GSA IAE team, other Government users and eventually to the public via a Web application (IE and Chrome browsers initially)

Enterprise Data Services Catalog

Create a comprehensive list of existing and planned API and Web Services, describe intended usage and map them to the prospective users (personas)

Make the Data Services Catalog available for the GSA IAE team, other Government users and eventually to the public via Web application (IE and Chrome browsers initially)

Data Classification - Define and manage

Reference Data

Core/Application Data

Audit Log Data

Metadata

Security Disposition

Data Model & Standards

Reviewing logical functional areas

Data Management Plan

Review, enhance, maintain current data management plan

Data Access Policy and Standards

Data Distribution and Retention Strategy, which at a minimum, defines parameters to Create and manage test data store and distribution

Refine legacy Data Migration Strategy

Define data lineage, including short-term and long-term data retention and storage policies

Operational Update Patterns

Create, Read, Update, Delete (CRUD) permissions on each item

System Interface analysis to determine methods to consolidate, optimize and/or deprecate interfaces

Data Interoperability Matrix which shows user and data interaction for Legacy systems and the new Modernized system (Business application by Personas)

Data Strategy and Roadmap

Documentation of the tasks, timelines, deliverables and processes which need to be established and completed for the system to be production ready (other artifacts developed may be referenced here)

Data Security

Data Security and Classification Standards

Data Security and Access Policies

Data Privacy Standards

Data Security Controls

Business Analytics Roadmap - metrics/design to capture

Who is accessing data?

Events and Triggers

Internal and External drivers

Access methods

Feedback mechanism to enhance performance

Reporting Strategy

Data Stewardship

Technical data stewardship documented which identifies key personnel, roles and responsibilities

Document the processes required to reconcile, update, connect and maintain data connectivity across the enterprise

Ensure the business rules established by the Business Stewards are documented and implemented in the appropriate data layer to ensure enforcement.

Sub-objective 2.3 User Interface and User Experience Support

The contractor shall provide the Government with technical leadership and expertise to support user interface development, including the SAM.gov (beta.sam.gov) front end and an open source library of common user interface components. The Front End Architect shall act as a technical liaison and representative for front end development in program-wide technical forums. The Front End Architect shall contribute to ongoing transformation of front end requirements, provided by the Government from legacy websites, into common, consolidated technical requirements and solutions. The Front End Architect shall collaborate with the Government and with technical and development staff from other contractor teams as provided in this Task Order by the contractor, to support the following activities.

Maintain, iteratively update, and socialize the front end technical strategy and roadmap

Maintain and iteratively update the front end architectural epics, features, and stories

Maintain, iteratively update, socialize, and coordinate implementation of front end technical standards, processes, and documentation including

Front end architecture documentation

Website information architecture / sitemap

Technology and tools documentation

Development environment best practices and standards

Software design best practices based on the approved technology stack

Software coding standards

Unit test processes and standards

Deployment strategy and processes

Accessibility standards and best practices

Represent front end development in technical discussions and decision making including those related to governance, platform, and deployment

Collaborate with the Government Internal Change Control Board and technical governance to document the methods by which changes to front end architecture, technology, standards, and processes are proposed, evaluated, approved, and captured

Support front end developer training activities held by the Government

The contractor shall provide the Government with user experience leadership and expertise to support user interface development, including the SAM.gov (beta.sam.gov) front end and an open source library of common user interface components. The User Experience Designer will provide expertise in transforming business requirements into user experiences that reduce burden and optimize value for a diverse user community. The User Experience Designer shall contribute to ongoing transformation of requirements, provided by the Government from legacy websites, into common, consolidated user experience requirements and design solutions. The User Experience Designer shall act as a user experience liaison and representative in program-wide forums. The User Experience Designer shall collaborate with the Government and with user outreach, design, and development staff from other contractor teams as provided in this Task Order by the contractor, to support the following activities.

Maintain and iteratively update user experience strategy, approach, roadmap, and best practices

Maintain and iteratively update visual and behavior standards for web pages and user interface controls including accessibility standards

Maintain and iteratively update style tiles, mood boards, and other conceptual tools

Maintain and iteratively update navigation and website workflow patterns

Collaborate with Government and contractor user analysts to solicit and incorporate user experience feedback

Create, maintain, and iteratively update wireframes and mock-ups and associated documentation

Represent user experience perspective in business and technical discussions

Collaborate and coordinate with the Government and contractor designers and front end developers to ensure user experience standards are followed

Support design training activities held by the Government

Objective 3 – Technical Governance and Requirement Support

To meet this objective the contractor shall provide the Government with Technical Governance Support and Technical Requirement Support. This support shall be achieves per the Sub-objectives as defined below:

1.

Technical Governance Support

2.

Technical Requirement Support

All IAE system modernization development work is directed in compliance with the Web Content Accessibility Guidelines 2.0 (WCAG 2.0) in anticipation of the Section 508 standards refresh.

Sub-objective 3.1 Technical Governance Support

The contractor shall support the Government in developing and maintaining IAE technical governance metrics and standards for the IAE environment. The contractor shall document all technical aspects of the environment and architecture to include the coding and development environments, micro services and API architecture, and data management to be contained in a Technical Governance Management Plan. The contractor shall develop and maintain the following artifacts as part of the Technical Governance Management Plan:

Documented Technical Architecture Standards which shall include approved Model-View-Controller (or appropriate) architectural patterns, components, and interactions.

Application Design Standards which shall ensure that standards are followed for all technical implementations, such as micro services and Application Program Interfaces (API), are validated, approved and cataloged.

Coding Standards which shall ensure coding & integration standards are being followed, identify potential scalability, interoperability or security issues, and facilitate the integration of the development teams and the code into the IAE technical community.

Technical Architecture Configuration Management Plan (sub plan) which shall document the methods by which changes to the architecture at any level are proposed, evaluated, approved and captured so as to maintain balance, flexibility, and control in the technical architecture;

Architecture Strategy which shall facilitate the transition of the architecture to evolve and meet Government needs in alignment with the roadmap

Section 508 Standards as per the WCAG 2.0 guidelines.

Release Process Management Plan (subplan) which shall document the plan, schedule, control and deliver applications (and their upgrades) through the different development, test, staging and production environments utilizing a “Pipeline” process and tools such as “Docker”.

Governance Measurements (Metrics): This shall include the collection of Scope, Cost, and Schedule, Sprint and Resource, as well as other metrics that convey the project’s velocity, throughput, backlog latency, and business efficacy.

Resource and Tools Management Plan and monitoring to proactively manage and oversee the need for filling gaps in technology, roles, skillsets, capabilities, etc.

The contractor shall support the administrative functions, to include the collection of meeting minutes, of the Internal Change Control Board (ICCB) processes and workflows, and assess architecture change requests to provide recommendations to the Government. The contractor shall support the Government in managing the corresponding changes as they occur through the design, development, and deployment cycles.

Sub-objective 3.2 Technical Requirements Support

The contractor shall provide technical requirements documentation support. The contractor shall document the technical requirements to support Agile development occurring within a CMMI standards based environment to ensure the benefits of both practices. Technical requirements shall be appropriately documented and maintained in the IAE collaborative environment, specifically Confluence. Technical requirement documentation support shall include:

Proposed technical requirements based on business and functional requirements provided by the Government

Documentation of technical requirements to be derived from business rules (such as within API documents or a business rules infrastructure)

Support for screen mockups and prototypes

Documentation of Technical Transition requirements provided by the Government for the new IAE environment (beta.sam.gov)

The contractor shall support the Government in documenting Government-defined technical requirements which reflect the business and functional requirements of IAE. The business and functional requirements shall be used to define the parameters of the technical requirements, the prioritized Quality Attributes of the SAM.gov application, and guide the application development parameters of the software developers. These technical requirements shall be captured and documented using the business and functional requirements as guidance, and with Government direction, review, and approval, shall be aligned with the IAE business processes. The contractor shall:

Perform usage analysis (and create corresponding artifacts) for each applicable software component to determine expected user interaction and capacity when deployed to production

Create ‘use cases’ that model typical user interaction on each module when deployed to production

Create a list of ‘system requirements’ that are derived from the business and functional requirements, use-cases and usage analysis

The contractor shall gather data, which shall include, but not limited to:

Tasks each user role will predominantly perform

Time of day for spikes in the number of users and their processing demands

Peak processing times for complex queries and what tasks are performed during these times

Expected duration of connectivity for each user Role in each module

Possible impacts of administrative functions (e.g. loading data, re-indexing tables, etc.) to users around the globe.

The contractor shall develop the Use Case models, which shall document the typical and atypical interaction for all users of the SAM.gov application, describing the complete workflow of interacting with the system from the perspective of each type (role) of user. The Use Cases shall be described in each of the following two methods:

Use Case diagrams that give a graphical depiction of the relationships between the actors (users) and the use cases (e.g. Relationship between Administrator and the Use Case for searching the Audit File)

Use Case reports which describe individual use cases, including primary and alternative workflows

Each Use Case shall include quantitative estimates about user behavior in the form of relative weights that will be used to determine high priority Quality Attributes (QA) such as performance, availability, usability, responsiveness, and other measures for quality of service. Relative ‘weights’ will be assigned to Use Cases by the contractor identifying the most common and critical user tasks. These “weights” will be reviewed by the Government.

The contractor shall develop the system technical requirements, utilizing the usage analysis and use cases, with the business and functional requirements. Examples of system technical requirements that affect design include, but not limited to:

Availability

Peak Capacity

Performance

Serviceability

Scalability

Securability

The contractor shall support the Government in the maintenance of API definitions that support technical requirements. The API definitions shall be evaluated for impact to the overall SAM.gov application, in order for the developers to have a clear understanding of the expectation of the API operations at the time of a release or the completion of a sprint. The Government will use these definitions both as part of the publication to API users, and to guide development of those APIs within IAE. The contractor shall document and maintain the following artifacts:

Technical Stories and specifications for components to support business processes

Non-functional (technical) requirements description documents

Identified and prioritized project Quality Attributes (QAs)

Use Case diagrams and Use Case reports

Usage Analysis Matrix and/or Report

5 Meeting Objectives To accomplish the Meeting Objectives of this Task Order the Contractor shall participate in the following meetings. Nothing discussed in any meetings or discussions between the Government and the Contractor shall be construed as adding, deleting, or modifying contractual agreement without written authorization from the Contracting Officer.

Meeting Objective 1 – Initial Business/Kickoff Meeting Within five (5) business days following the Task Order award date (or other time mutually agreed between the parties), the Contractor representatives will meet with the the GSA Contracting Officer, GSA COTR, and Government program manager or designee to review the contractor’s understanding of the requirements, goals and objectives of this task order. The contractor shall also address the status of any issues that will affect contractor start-up/ramp-up toward achieving full service/support capability. The Government will be responsible for taking minutes of this meeting.

Meeting Objective 2 – Ad hoc Technical / Work Status / Administrative Meetings

The Contractor shall, if requested by the Government, participate in monthly status meetings or ad hoc technical meetings or ad hoc work status meetings at a mutually agreeable time and place to discuss tasking, work progress, technical problems, performance issues, or other technical matters. During these meetings the Contractor shall at least provide accomplishments, problems and issues and planned actions. The Contractor shall take minutes of these meetings and include them in a Monthly Status Report (Data Item A003). These meetings will occur at a time and place mutually agreed upon by the parties.

Meeting Objective 3 – Contract Administration Meetings The Contracting Officer (CO) may require the authorized Contractor representative to meet or participate in a teleconference with authorized Government personnel as often as deemed necessary to discuss contract performance or administrative issues. The Contractor may also request a meeting with the CO when deemed necessary. The content of meetings shall be documented in writing. Minutes shall be approved by both parties and shall be included in the Government contract file.

6 Contract-wide Objectives

Contract-wide Objective 1 – Contract and Project Management

The Contractor shall be solely responsible for managing the work performed in the execution of this contract/order. This includes the responsibility to –

· assign appropriate resources to each task,

· maintain clear organizational lines of authority,

· ensure effective contract task management and administration

· establish and use proven policies, processes, analyses, and best practices

The Contractor shall maintain project milestones for each assigned task. The Contractor shall coordinate all work with the ASC/WWQ, F-15 Program Office. The Contractor shall update Government representatives on work progress and task milestones during the monthly status meetings.

Contract-wide Objective 2 – Subcontract Management

The Contractor shall be fully responsible for management, control, and performance of any Subcontractor used on this contract. If a Subcontractor is being used, the Prime Contractor must inform the Government. Use of a Subcontractor on the Contractor’s team shall not relieve the Prime Contractor of responsibility nor accountability in the execution of this contract/order.

Contract-wide Objective 3 – Business Relations

A primary element of project success is the business relationship between the Contractor and Government representatives. Within this context the Government will monitor the Contractor’s contribution to business relations and provide feedback when required. The Contractor shall make every effort to establish and maintain clear and constant communication channels with the Government primaries (CO, COTR, and Government Technical Representative) of this contract for the purpose of:

· Promptly identifying PWS and/or business relationship issues of controversy and the bilateral development and implementation of corrective action plans.

· Ensuring the professional and ethical behavior of Contractor personnel.

· Maintaining effective and responsive Subcontractor management.

· Ensuring the Contractor support team is fully aware and engaged in strengthening the interdependency that exists between the Contractors and their Government counterparts.

· Facilitating Contractor–Government collaboration for continuous improvement in the conduct of PWS tasks, reducing risks, costs and meeting the mission…