ATT L - Service Catalog Descriptions - Draft.pdf

ATTACHMENT L

NASA CONSOLIDATED APPLICATIONS AND

PLATFORM SERVICES (NCAPS)

SERVICE CATALOG DESCRIPTIONS

RFP 80TECH22R0002

CONTRACT #TBD

DATE: TBD

NCAPS Contract – 80TECH22R0002 Attachment L Service Catalog Descriptions

Table of Contents Attachment L Introduction

Teams SAFe Agile Release Train (ART) Team Agile Product Team Two-Week Sprints/Iterations (Various Sizes) ABAP Special Use Developers Shared Services Team Two-Week Sprints/Iterations (Various Sizes) SAP BASIS Specialized Software Integration Shared Services Team Two-Week Sprints/Iterations (Various Sizes) ColdFusion Developers Shared Services Team Two-Week Sprints/Iterations (Various Sizes) Web Application Integration Shared Services Team Two-Week Sprints/Iterations (Various Sizes) Cybersecurity Specialist Team Shared Services Team Two-Week Sprints/Iterations (Various Sizes) Access Management Shared Services Team Two-Week Sprints/Iterations (Various Sizes) Technical Writers Shared Services Team Two-Week Sprints/Iterations (Various Sizes) Configuration Management Shared Services Team Two-Week Sprints/Iterations (Various Sizes) Release Management Shared Services Team Two-Week Sprints/Iterations (Various Sizes) Platform Management Shared Services Team Two-Week Sprints/Iterations (Various Sizes) Database Support Shared Services Team Two-Week Sprints/Iterations (Various Sizes) Business Intelligence (BI) and Data Modeling Team Two-Week Sprints/Iterations (Various Sizes) Process Automation Shared Services Team Two-Week Sprints/Iterations (Various Sizes) 2-Week Iteration/Sprint Agile Product Team and Shared Services Team Reports Agile Release Train (ART) Program Increment Reports Quarterly/Program Increment Agile Product Team and Shared Services Team Health Radar Report Bi-Annual Role-Based Health Radar Reports

O&M Bundles KSC Infrastructure and Application O&M Bundled Services (Group name)

Application and System O&M Application O&M Services Infrastructure and Application Extended Support for Agency Commercial SSL Certificate

Application and System Development Investigation Report Application Development Small Development Startup and Close Down Medium Development Startup and Close Down Large Development Startup and Close Down Full 7120.7 support addon to Development Startup and Close Down

SharePoint as a Service SharePoint as a Service (SPaaS) - Site Collection High Availability SharePoint as a Service (SPaaS) - Site Collection SharePoint Custom Solution Review SharePoint Mirror Test Site Defined SharePoint Training

Process Automate Process Automation Discovery Automation Development Sprint Services Sprint 0 Automation Development Sprint Services Sprint (Extra Small) Automation Development Sprint Services Sprint (Small) Automation Development Sprint Services Sprint (Medium) Automation Development Sprint Services Sprint (Large) O&M Attended Automation (Extra Small) O&M Attended Automation (Small) O&M Attended Automation (Medium) O&M Attended Automation (Large) O&M Unattended Automation (Extra Small) O&M Unattended Automation (Small) O&M Unattended Automation (Medium) O&M Unattended Automation (Large)

Attachment L Introduction

This appendix specifies the orderable catalog offerings for both Standard and Ancillary Services.

Each offering contains the following items:

• Catalog Description

• Catalog ID(s)

• Applicable PWS Requirement(s) o NOTE: The requirements of PWS elements 1.0 through 4.0 apply to all NCAPS products and services and, as such, are not specifically enumerated.

• Description at a summary level, which is not intended to duplicate or take precedence over Attachment J-01, Performance Work Statement (PWS) o NOTE: This includes Deliverable Products and Services (DPS) consumption information for Standard Services, if not self-explanatory in Attachment B, Deliverable Products and Services.

• Unique Considerations

Catalog offerings required for NCAPS to internally fulfill contract requirements are prohibited from being billed to the Government. In addition, catalog offerings that are specifically stated as included in the Description of a service and/or identified as part of a Unique Consideration, shall not be separately charged to the Government.

Teams

Catalog Description SAFe Agile Release Train (ART) Team

Catalog ID(s) FPT-001

Applicable PWS Requirement(s)

7.0; 7.5

Description This catalog item is to order an ART Team needed to manage from 50 – 125 people organized in 5 to 12 multiple agile product teams and shared services teams as part of a single ART. As part of the Scaled Agile Framework for Lean Enterprises (SAFe), an ART is a team of Agile teams, which, along with other stakeholders, incrementally develops, delivers, and operates, one or more solutions in a value stream.

Unique Considerations

This catalog is only needed when the Government determines the Agile teams need to be managed as part of an ART. If the Government determines there is no need to manage a group of Agile teams as part of an ART, then there is not requirement to order an ART team.

This catalog offering requires that at least 5 Agile Product Teams or Shared Services Teams (FPT-002 thru FPT-056) are ordered.

Description Agile Product Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-00, FPT-003, FPT-004

Applicable PWS Requirement(s)

7.0; 7.1; 7.3; 7.4; 7.6

An agile product team is a cross-functional group of individuals who can define, build, test, and deploy an increment of value in a brief timebox and includes a Scrum Master. A contractor-led agile product team relies on the contractor to fill the roles that are not inherently governmental:

scrum master, and other agile team members.

• Small – Teams will deliver 40+ Story Points per 2-week iteration.

• Medium – Teams will deliver 56+ Story Points per 2-week iteration.

• Large – Teams will deliver 72+ Story Points per 2-week iteration

Unique Considerations

Teams requiring specialized roles, skills, and services to support the success of multiple product teams or an Agile Release Train (ART) may be better suited as a “Shared Services Team” rather than an “Agile

Product Team.” The Government will determine if a shared services team is needed and order it accordingly.

Description

ABAP Special Use Developers Shared Services Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-005, FPT-006, FPT-007, FPT-008

Applicable PWS Requirement(s)

7.0; 7.2; 7.3; 7.4; 7.6

Description This is to order an Advanced Business Application Programming (ABAP) development shared services team to design and creating software programs and applications through the SAP and ABAP programming codes.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master, and other agile team members.

• X-small – Teams will deliver 24+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

• Medium – Teams will deliver 56+ Story Points per 2-week iteration

• Large – Teams will deliver 72+ Story Points per 2-week iteration

Shared Services personnel engage in the following type of activities:

Participating in Program Increment (PI) Planning as well as Pre- and Post- PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of ABAP developer and

Scrum Master skills.

SAP BASIS Specialized Software Integration Shared Services Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-009, FPT-010, FPT-011, FPT-012

Applicable PWS Requirement(s)

7.0; 7.2; 7.3; 7.4; 7.6

Description This is to order a Business Application Software Integrated Solution (BASIS) development shared services team to design and creating software programs and applications using BASIS.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master, and other agile team members.

• X-small – Teams will deliver 24+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of SAP BASIS developer and

ColdFusion Developers Shared Services Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-013, FPT-014, FPT-015, FPT-016

Applicable PWS Requirement(s)

7.0; 7.2; 7.3; 7.4; 7.6

Description This is to order a ColdFusion development shared services team to design and creating software programs and applications using ColdFusion.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master, and other agile team members.

• X-small – Teams will deliver 24+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of Cold Fusion developer and

Web Application Integration Shared Services Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-017, FPT-018, FPT-019, FPT-020

Applicable PWS Requirement(s)

7.0; 7.2; 7.3; 7.4; 7.6

Description This is to order a Web Application Integration shared services team to provide web application integration support for applications maintained or managed by NCAPS.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master, and other agile team members.

• X-small – Teams will deliver 24+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of Web Application Integration and Scrum Master skills.

Cybersecurity Specialist Team Shared Services Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-021, FPT-022, FPT-023, FPT-024

Applicable PWS

7.0; 7.2; 7.3; 7.4; 7.6

This is to order a Cybersecurity Specialist to develop and maintain Security plans for applications maintained or managed by NCAPS.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master, and other agile team members.

• X-small – Teams will deliver 24+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of Cybersecurity and Scrum Master skills.

Access Management Shared Services Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-025, FPT-026, FPT-027, FPT-028

Applicable PWS Requirement(s)

7.0; 7.2; 7.3; 7.4; 7.6

Description This is to order an Access Management shared services team to perform access management for applications maintained or managed by NCAPS.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master and other agile team members.

• X-small – Teams will deliver 24+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of Access Management and

Technical Writers Shared Services Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-029, FPT-030, FPT-031, FPT-032

Applicable PWS Requirement(s)

7.0; 7.2; 7.3; 7.4; 7.6

Description This is to order Technical Writer skills to develop and maintain documentation for NCAPS managed applications.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master, and other agile team members.

• X-small – Teams will deliver 24+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of Technical Writer and

Configuration Management Shared Services Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-033, FPT-034, FPT-035, FPT-036

Applicable PWS Requirement(s)

7.0; 7.2; 7.3; 7.4; 7.6

Description This is to order Configuration Management skills to manage the configuration of NCAPS managed applications.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master, and other agile team members.

• X-small – Teams will deliver 28+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of Configuration Management and Scrum Master skills.

Release Management Shared Services Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-037, FPT-038, FPT-039 FPT-040

Applicable PWS Requirement(s)

7.0; 7.2; 7.3; 7.4; 7.6

Description This is to order Release Management skills to manage releases for NCAPS managed applications.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master and other agile team members.

• X-small – Teams will deliver 24+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of Release Management and

Platform Management Shared Services Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-041, FPT-042, FPT-043, FPT-044

Applicable PWS Requirement(s)

7.0; 7.2; 7.3; 7.4; 7.6

Description This is to order a Platform Management shared services team to manage platform services for NCAPS managed applications.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master and other agile team members.

• X-small – Teams will deliver 24+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of Platform Management and

Database Support Shared Services Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-045, FPT-046, FPT-047, FPT-048

Applicable PWS Requirement(s)

7.0; 7.2; 7.3; 7.4; 7.6

Description This is to order Database skills to implement and manage NCAPS managed databases.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master and other agile team members.

• X-small – Teams will deliver 24+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of Database Administrator and Scrum Master skills.

Business Intelligence (BI) and Data Modeling Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-049, FPT-050, FPT-051, FPT-052

Applicable PWS Requirement(s)

7.0; 7.2; 7.3; 7.4; 7.6

Description This is to order a Business Intelligence (BI) and Data Modeling development shared services team to design and creating software programs and applications.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master and other agile team members.

• X-small – Teams will deliver 24+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of Business Intelligence, Data Modeling and Scrum Master skills.

Process Automation Shared Services Team Two-Week Sprints/Iterations (Various Sizes)

Catalog ID(s) FPT-053, FPT-054, FPT-055, FPT-056

Applicable PWS Requirement(s)

7.0; 7.2; 7.3; 7.4; 7.6

Description This is to order a Process Automation development shared services team to design and creating software programs and applications.

A contractor-led shared services team relies on the contractor to fill the roles that are not inherently governmental: scrum master and other agile team members.

• X-small – Teams will deliver 24+ Story Points per 2-week iteration

• Small – Teams will deliver 40+ Story Points per 2-week iteration

PI Planning.

Driving requirements where necessary, adding to solution intent and taking ownership of their portion of dependent backlog items.

Collaborating with Agile Product Teams to fulfill the dependencies that occur during PI execution.

Participating in System Demos and Solution Demos and Inspect and Adapt (I&A) workshops, when appropriate, as many improvement backlog items may reflect challenges with the availability of specialized skills and dependencies.

Unique Considerations

Any deliverables produced by a shared services team should remain the deliverable of the shared services team and the shared services teams’ velocity should not be included in the agile product team’s velocity. If a part of a deliverable is delivered by another team, i.e., shared services team, then the velocity should be reduced to account for the reduction in complexity to provide the deliverable.

This Shared Services Team is only made up of Process Automation and

Description Inspect and Adapt (I&A) Team One-Week Event (Various Sizes)

Catalog ID(s) FPT-057, FPT-058, FPT-059, FPT-060, FPT-061

Applicable PWS Requirement(s)

7.9

Description This is to order agile teams, shared services teams, and ART teams for a one-week Inspect and Adapt (I&A) event with the following output:

• I&A Team (X-Small): Expected output equivalent to 12+ story points

• I &A Team (Small): Expected output equivalent to 20+ story points

• I&A Team (Medium): Expected output equivalent to 28+ story points

• I&A Team (Large): Expected output equivalent to 36+ story points

• SAFe Agile Release Train (ART) I&A Team: Manage 500+ stories per each one week I&A event

Unique Considerations

I&A event activities are calculated by story points. If an I&A team’s capacity is greater than the number of I&A story points, the team should continue to work items from their respective backlog(s) to make use of the team’s full capacity.

2-Week Iteration/Sprint Agile Product Team and Shared Services Team Reports

Catalog ID(s) FPT-062

Applicable PWS

7.7 A, B.i; 7.8 A

At the end of each 2-week iteration/sprint, each agile team will provide the following:

• Flow Distribution for the Team

• Flow Velocity with Flow Velocity Fluctuations for the Team

• Flow Time for the Team

• Flow Efficiency for the Team

• Flow Load for the Team

• Commitment Reliability for the Team

• Burndown and Burnup charts for the Team

Reports will be generated using Government provided tools (i.e., Agility Health, Jira Align, etc.) Reference “ATT G - Acronyms and Abbreviations” for definitions and examples.

One of this catalog offering must be ordered for each Agile Product Teams or Shared Services Teams (FPT-002 thru FPT-056) that will product these reports.

Description Agile Release Train (ART) Program Increment Reports

Catalog ID(s) FPT-063

Applicable PWS Requirement(s)

7.7 A, B.ii; 7.8 B

Description At the end of each Program Increment each ART will provide the following:

• Flow Distribution for the ART

• Flow Velocity for the ART

• Flow Time for the ART

• Flow Efficiency for the ART

• Flow Predictability for the ART and for each agile team in the ART

Reports will be generated using Government provided tools (i.e., Agility Health, Jira Align, etc.) Reference “ATT G - Acronyms and Abbreviations” for definitions and examples.

This catalog offering must be ordered in combination with SAFe Agile Release Train (ART) Team (FPT-001).

Quarterly/Program Increment Agile Product Team and Shared Services Team Health Radar Report

Catalog ID(s) FPT-064

Applicable PWS Requirement(s)

7.7 A, B.iii; 7.8 C

Description At the end of each quarter or Program Increment the following report will be provided:

• Team Health Radar for each Team

Reports will be generated using Government provided tools (i.e., Agility Health, Jira Align, etc.) Reference “ATT G - Acronyms and Abbreviations” for definitions and examples.

Description Bi-Annual Role-Based Health Radar Reports

Catalog ID(s) FPT-065

Applicable PWS Requirement(s)

7.7 A, B.iv; 7.8 D-F

Description The following reports will be provided twice a year:

• Scrum Master Health Radar

• Product Owner Health Radar

• Release Train Engineer Health Radar

Unique Considerations

Reports will be generated using Government provided tools (i.e., Agility Health, Jira Align, etc.) Reference “ATT G - Acronyms and Abbreviations” for definitions and examples.

O&M Bundles

KSC Infrastructure and Application O&M Bundled Services (Group name)

Catalog ID(s) KSC-001-A, KSC-002-S, KSC-003-A, KSC-004-S, KSC-005-A, KSC-

006-A, KSC-007-A, KSC-008-S, KSC-009-S, KSC-010-S, KSC-011-A,

KSC-012-A, KSC-013-S, KSC-014-A, KSC-015-S, KSC-016-S, KSC-

017-A, KSC-018-A, KSC-019-S, KSC-020-S, KSC-021-A

Applicable PWS

8.0; 8.1; 8.1.1

This catalog offering is a combined offering providing operations and maintenance (O&M), support to Service Customers, platform management, investigation requests, system configuration, defect and bug resolution, and access control for wide variety of applications, websites and systems. This catalog offering is a bundle of services for the KSC OCIO customers, with support for both local and Agency Service Customers. The KSC Infrastructure and Application O&M Bundled Services catalog offering provides full support needed to operate and maintain the applications, websites, and systems.

Applications will be assigned the appropriate number of points based on the definitions in Attachment K, Application Support Levels.

This catalog offering includes the quantity of Application Points specified in Attachment P, Deliverable Products and Services, per the Catalog ID.

Systems are defined as offerings that do not meet the application definitions defined in Attachment K, Applications Support Levels, definition and require one or more of the following:

Dedicated virtual/physical assets that run a server operating system Non-Production languages per the AP-NASA-HDBK-001, Applications

Program Handbook

Systems supported under this catalog item are listed in Attachment S, Application Inventory, as belonging to the indicated Catalog ID.

The Catalog IDs to Group Naming for the Catalog items are listed below.

Catalog ID Group Name KSC-001-A OCIO (Apps) KSC-002-S OCIO (Systems) KSC-003-A CESO (Apps) KSC-004-S CESO (Systems) KSC-005-A OP (Apps) KSC-006-A CFO (Apps)

KSC-007-A OSI (Apps) KSC-008-S OSI (Systems) KSC-009-S OPS (Apps) KSC-010-S OPS (Systems) KSC-011-A OCOMM (Apps) KSC-012-A OCHCO (Apps) KSC-013-S OCHCO (Systems) KSC-014-A OCHMO (Apps) KSC-015-S CCP (Systems) KSC-016-S EGS (Systems) KSC-017-A HEO (Apps) KSC-018-A OCT (Apps) KSC-019-S OSI (Maximo) (Systems) KSC-020-S OCIO (Enterprise Architect) (Systems)

KSC-021-A

Customers not approved by the Technical Monitor (TM) must order Ancillary catalog offering Infrastructure and Application O&M Services (A-001).

Applications in the SaaS support level still require inclusion in an IT System Security Plan (ITSSP) in accordance with PWS 4.0, Cybersecurity Services Overview, but development of the ITSSP is not included in the scope of this offering.

Application and System O&M

Description Application O&M Services

Catalog ID(s) OM-001

Applicable PWS

8.0; 8.1; 8.1.1

This catalog offering is an Ancillary Service with support for OCIO, Program, and Agency customers. This offering provides full application, website, and platform operations and maintenance, including application and website defect and bug resolution, platform configuration, management, and problem resolution, Service Customer support, and access control.

This catalog offering includes the required application platform licensing in accordance with the AP-NASA-HDBK-001, Applications Program Handbook.

The unit of measure for this catalog offering is per Application Point.

Each application is assigned a number of Application Points based on the Application Support Level criteria specified in Attachment K, Applications Support Levels.

Non-production environments provided to external parties under “Hosted Only” are considered production environments for the purposes of ATT M, Fixed Price Catalog Item Service Delivery Standards and Metrics.

Applications in the SaaS support level still require inclusion in an IT System Security Plan (ITSSP) in accordance with PWS 4.0, Cybersecurity Services Overview, but development and maintenance of the ITSSP is not included in the scope of this offering.

This offering cannot be utilized to order support for a System.

Description Infrastructure and Application Extended Support for Agency

Catalog ID(s) OM-002

Applicable PWS

8.1; 8.1.3

Description This catalog offering provides the extension of the Standard Hours and provides support to Agency applications across multiple time zones.

This catalog offering requires that the application is either:

Part of one of the Application O&M Bundles, or Ordered in combination with Application O&M Services (OM-001)

Description Commercial SSL Certificate

Catalog ID(s) OM-003

Applicable PWS

8.1.1 Q

Description This catalog offering provides the procurement, installation and maintenance of a Commercial SSL Certificate.

This catalog offering requires that the application is either:

Part of one of the Application O&M Bundles, or Ordered in combination with Application O&M Services (OM-001)

Application and System Development

Description Investigation Report

Catalog ID(s) DEV-001

Applicable PWS

8.0 B

This catalog offering provides an analysis of requirements and capabilities with a report describing the potential solution(s). The report is used by the TM for planning purposes.

Unique

N/A

Description Application Development

Catalog ID(s) DEV-002

Applicable PWS

8.0 (Excluding B, M-P); 8.1; 8.1.2 (Excluding A, I)

This catalog offering provides an offering of Incremental Development Units (IDU) for new application development and enhancements to existing applications. This catalog offering is used to provide development and documentation of a production ready product for a wide variety of applications, websites and systems supporting OCIO, Program and Agency customers. Delivery of this catalog offering provides the TM and SC with a fixed review cycle and incremental approval of the development project portions being delivered.

The IDUs consumed by this catalog offering may be scaled in accordance with Attachment J, Fixed Price Sprint Story Point Process, to create Iterations.

If the IDU is not characterized as an Enhancement IDU type, this catalog offering will require ordering one of the following: Small Development Startup and Close Down (B-002), Medium Development Startup and Close Down (B-003), Large Development Startup and Close Down (B- 004).

This catalog offering requires immediate allocation of Application Points under Infrastructure and Application O&M Bundled Services (001-S) or must be ordered in combination with Infrastructure and Application O&M Services (A-001) if the Government requires services provided under the O&M catalog item.

Description Small Development Startup and Close Down

Catalog ID(s) DEV-003

Applicable PWS

8.0 A, E-H; 8.1; 8.1.2 A (except vi.), F-I

This catalog offering provides an offering to support the activities required to start and end a development project built on a COTS platform that supports custom extensions as described in Attachment J, Fixed Price Sprint Story Point Process.

This catalog offering must be ordered at the initiation of Application Development (DEV-002) for activities not categorized as an Enhancement IDU type.

Description Medium Development Startup and Close Down

Catalog ID(s) DEV-004

Applicable PWS required to start and end a development project that is planned to consume fewer than 30 IDUs. This catalog offering is not used for an Enhancement IDU type as described in ATT J, Fixed Price Sprint Story Point Process, or for the COTS platforms described under the Small Development Startup and Close Down (DEV-003) catalog offering.

Unique Considerations

This catalog offering must be ordered at the initiation of Application Development (DEV-002) for activities not categorized as an Enhancement IDU type.

If development under Medium Development Startup and Close Down (DEV-004) exceeds the 35 IDUs then a Large Development Startup and Close Down (DEV-005) must be ordered in place of the Medium Development Startup and Close Down (DEV-004).

Description Large Development Startup and Close Down

Catalog ID(s) DEV-005

Applicable PWS required to start and end a development project that is planned to consume 30 or more IDUs as described in Attachment J, Fixed Price Sprint Story Point Process.

Unique Considerations

This catalog offering must be ordered at the initiation of Application Development (DEV-002) for activities not categorized as an Enhancement IDU type.

If development under Medium Development Startup and Close Down (DEV-004) exceeds the 35 IDUs then a Large Development Startup and Close Down (DEV-005) must be ordered in place of the Medium Development Startup and Close Down (DEV-004).

Description Full 7120.7 support addon to Development Startup and Close Down

Catalog ID(s) DEV-006

Applicable PWS

8.1.2 A vi, 8.1.2 D vii, 8.1.2 I ix, This catalog offering provides an offering to enhance the 7120.5 and

7150.2 requirements to provide up to full compliance.

Unique Considerations

This catalog offering requires one of the following are ordered:

Ordered in combination with Small Development Startup and Close

Down (DEV-003) or Ordered in combination with Medium Development Startup and Close

Down (DEV-004) or Ordered in combination with Large Development Startup and Close

Down (DEV-005) or

SharePoint as a Service

Description SharePoint as a Service (SPaaS) - Site Collection

Catalog ID(s) SP-001

Applicable PWS

8.1.4 A-T

This catalog offering provides SharePoint Site Collections in a Software as a Service (SaaS) model with multiple storage options. This catalog offering includes all software, licensing, hosting, and custom components necessary to deliver the Site Collection. Site collections are available with the following Enhanced tier storage allocations:

10 Gigabytes (GB)

25 GB

50 GB

100 GB

100 GB increments

This catalog offering is delivered with Application Criticality 2 as described in Attachment M, Fixed Price Catalog Item Service Delivery Standards and Metrics, and includes catalog offering Infrastructure and Application Extended Support for Agency (OM-002).

Description High Availability SharePoint as a Service (SPaaS) - Site Collection

Catalog ID(s) SP-002

Applicable PWS

8.1.4 A-S, U, V

This catalog offering provides SharePoint Site Collections in a Software as a Service (SaaS) model with multiple storage options. This catalog offering includes all software, licensing, hosting, and custom components necessary to deliver the Site Collection. Site collections are available with the following Enhanced tier storage allocations:

10 Gigabytes (GB)

25 GB

50 GB

100 GB

100 GB increments

This catalog offering is delivered with Application Criticality 1 as described in Attachment M, Fixed Price Catalog Item Service Delivery Standards and Metrics, and includes catalog offering Infrastructure and Application Extended Support for Agency (OM-002).

To be provided within 1 year of the contract start date.

Description SharePoint Custom Solution Review

Catalog ID(s) SP-003

Applicable PWS Requirement(s)

8.1.4 W

Description This catalog offering provides for the review of a Customer Developed SharePoint.

Unique

Description SharePoint Mirror Test Site

Catalog ID(s) SP-004

Applicable PWS Requirement(s)

8.1.4 X

Description Provide and maintain a SharePoint Mirror Test Site.

Unique

Description Defined SharePoint Training

Catalog ID(s) SP-005-i, SP-005-ii, SP-005-iii, SP-005-iv, SP-005-v, SP-005-vi, SP-005-vii

Applicable PWS

8.1.4 Y, Z

Description Provide the following Training classes.

• SharePoint Basic Training (Self-Paced with completion review)

• SharePoint Advanced Training (Self-Paced with completion review)

• SharePoint Designer (Self-Paced with completion review)

• Power Apps

• Power Automate

• Nintex

• SharePoint Framework Development

Unique

Process Automate

Description Process Automation Discovery

Catalog ID(s) PA-A-001

Applicable PWS Requirement(s)

11.1; 11.2

Description Sprint Zero A subject matter expert in Intelligent Automation will engage with the customer to review requirements, understand the entire process from beginning to finish, and formulate the best path forward for the required automation. This service is not about just accepting customer requirements as is, but fully understanding what the requirements are with the expertise in intelligent automation offerings to best fulfill the requirement, even if it meant adjusting the customer original requirements. Discovery is likely to require 2-3 meetings with the customer with the delivery of scoped requirements in JIRA, required SCI’s to deliver the automation and a process automation flow chart.

Considerations N/A

Description Automation Development Sprint Services Sprint 0

Catalog ID(s) PA-A-002

Applicable PWS Requirement(s)

11.1; 11.3

Description Sprint 0 Development team working the duration of the sprint communicating with the customer stakeholders to design and architect the intelligent automation solution that meets the customer requirements. The team will develop process design specifications documentation, a groomed backlog of functional user stories, product wireframe designs (optional), a projected development sprint schedule, security review and project infrastructure setup (servers, DevOps Suite, etc.). The sprint covers a two-week period with the deliverable being the fully completed JIRA backlog and sprint 1 grooming. The development stories will add up to 14 points.

Deliverables:

1. Sprint Schedule with milestone delivery dates.

2. Sprint Report

3. All Items Delivered

a. Documentation

b. Completion of sprint stories defined by sprint size

c. Customer story completion acceptance

4. Customer Demo

5. User Acceptance Testing (as needed)

6. Security Review and Scanning

7. Push to production (if applicable)

Unique Considerations N/A

Catalog Description Automation Development Sprint Services Sprint (Extra Small)

Catalog ID(s) PA-A-003

Applicable PWS Requirement(s) 11.1; 11.3

Description Development Extra Small Sprint – Developer(s) working the duration of the sprint where the end deliverable of the sprint is deployment of the completed stories to the production environment. The expected customer for this sprint would be looking for a very straightforward automation that has very low complexity and minimal customer interaction required. This consists of development, testing, security scanning and deployment. Each sprint will conclude with a customer demonstration of the functionality with signoff that all sprints were completed. The sprint covers a two-week development/test/deploy cycle, and the development stories will add up to 3 points.

Deliverables:

1. Sprint Schedule with milestone delivery dates.

2. Sprint Report

3. All Items Delivered

a. Documentation

b. Completion of sprint stories defined by sprint size

c. Customer story completion acceptance

4. Customer Demo

5. User Acceptance Testing (as needed)

6. Security Review and Scanning

7. Push to production (if applicable)

Unique

Description Automation Development Sprint Services Sprint (Small)

Catalog ID(s) PA-A-004

Applicable PWS Requirement(s)

11.1; 11.3

Description SCI-01 Small Developer(s) working the duration of the sprint where the end deliverable of the sprint is deployment of the completed stories to the production environment. The expected customer for this sprint would be looking for a fairly straightforward automation that has low complexity and minimal customer interaction required. This consists of development, testing, security scanning and deployment. Each sprint will conclude with a customer demonstration of the functionality with signoff that all sprints were completed. The sprint covers a two-week development/test/deploy cycle, and the development stories will add up to 8 points.

Deliverables:

1. Sprint Schedule with milestone delivery dates.

2. Sprint Report

3. All Items Delivered

a. Documentation

b. Completion of sprint stories defined by sprint size

c. Customer story completion acceptance

4. Customer Demo

5. User Acceptance Testing (as needed)

6. Security Review and Scanning

7. Push to production (if applicable)

Description Automation Development Sprint Services Sprint (Medium)

Catalog ID(s) PA-A-005

Applicable PWS Requirement(s)

11.1; 11.3

Description SCI-02 Medium A suggested team of a developer and a process automation SME working in tandem to deliver the sprint (skill sets may be altered depending on the work to be performed). While 2 roles are identified, it isn’t expected that 100% of each would be dedicated to the sprint. The expected customer for this sprint would have a more complex process that requires intelligent automation that may require multiple software interactions as well as some minor custom coding. The process is complex enough that a process automation SME would take a larger role in assisting the customer through the process and act as a facilitator for questions and updates. This consists of development, testing, security scanning and deployment. Each sprint will conclude with a customer demonstration of the functionality with signoff that all sprints were completed. The sprint covers a two-week development/test/deploy cycle, and the development stories will add up to 20 points Deliverables:

1. Sprint Schedule with milestone delivery dates.

2. Sprint Report

3. All Items Delivered

a. Documentation

b. Completion of sprint stories defined by sprint size

c. Customer story completion acceptance

4. Customer Demo

5. User Acceptance Testing (as needed)

6. Security Review and Scanning

7. Push to production (if applicable)

Description Automation Development Sprint Services Sprint (Large)

Catalog ID(s) PA-A-006

Applicable PWS Requirement(s)

11.1; 11.3

Description SCI-03 Large A suggested team of 2 developers, a process automation SME, and a technical architect working in tandem to deliver the sprint (skill sets may be altered depending on the work to be performed). The expected customer for this sprint would have a complex project that may require multiple software interactions with API’s, GUI or cloud connections to fully complete the automation. The process will likely consist of multiple steps that the process automation SME will need to outline and ensure each step is fully understood for each story under development. The technical architect may be needed if other services are required within the process that are not fully understood. This consists of development, testing, security scanning and deployment. The sprint covers a two-week development/test/deploy cycle, and the development stories will add up to 40 points.

Deliverables:

1. Sprint Schedule with milestone delivery dates.

2. Sprint Report

3. All Items Delivered

a. Documentation

b. Completion of sprint stories defined by sprint size

c. Customer story completion acceptance

4. Customer Demo

5. User Acceptance Testing (as needed)

6. Security Review and Scanning

7. Push to production (if applicable)

Description O&M Attended Automation (Extra Small)

Catalog ID(s) PA-B-001

Applicable PWS Requirement(s)

11.1; 11.4

Description These automations are unlikely to generate a large number of break/fixes, nor will they have frequent updates. These are very low complexity, very low step automations that are straightforward. This line item will cover O&M for break/fixes only, no new functionality. All new functionality will require a new catalog request purchase. As part of the break/fix process, any updates requiring documentation changes will be handled by the assigned developer. New versions of the attended automation will be provided to the impacted individuals for update after testing is complete.

Description O&M Attended Automation (Small)

Catalog ID(s) PA-B-002

Applicable PWS Requirement(s)

11.1; 11.4

Description These automations are unlikely to generate a large number of break/fixes, nor will they have frequent updates.