AFLDP-IT_BPA_Attachment_1_PWS_DRAFT.pdf

CUI

Solicitation FA7014‐25-Q-0001

PERFORMANCE WORK STATEMENT

FOR

AIFORCE LEADERSHIP DEVELOPMENT PROGRAM- INFORAMTION

TECHNOLOGY (AFLDP-IT)

AT

THE PENTAGON, WASHINGTON, D.C. & JOINT BASE SAN ANTONIO, TEXAS

06 NOVEMBER 2024

V 1.9

Controlled by: AFDW/PK CUI Categories: PROCURE Distribution/Dissemination Controls:

OPEN PRE-AWARD

POC: ASHLEY RAYMOND

Coordination and Review:

AMANDA ROBERTS Signature Date

AF/A1XR

A1 Contracts Manager

BLAKE PATTON Signature Date

AF/A1 DTA/DTAC

PROGRAM MANAGER

BRANDON ERPELDING Signature Date

AF/A1 DTA/DTAC

COR

ANTHONY ROGERS Signature Date

AFDW/PKP

QAPC

ASHLEY RAYMOND Signature Date

AFDW/PKH

Contracting Officer

Contents

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General

SECTION II

2.0 TASK DESCRIPTIONS

2.1 TASK 1: PLATFORM PROJECT MANAGEMENT SUPPORT

2.1.1 SUB TASK 1: CONVENE TECHINCAL STATUS MEETINGS

2.1.2 SUB TASK 1: DEVELOP PLANS AND REPORTS

2.2 TASK 2: PLATFORM HELPDESK AND SYSTEM ADMINISTRATION

SUPPORT

2.3 TASK 3: BOARD SUPPORT

2.4 TASK 4: SOFTWARE DEVELOPMENT, IMPROVEMENT AND

MODIFICATION

2.5 TASK 5: SOFTWARE IMPLEMENTATION

2.6 TASK 6: SOFTWARE MAINTENANCE

2.7 TASK 7: APPLICATION WEBSITE MANAGEMENT AND SUPPORT

2.8 TASK 8: INFORMATION ASSURANCE (IA) AND SYSTEM SECURITY

SUPPORT

2.9 TASK 9: TRAINING

SECTION III

3.0 SERVICE SUMMARY

SECTION IV

4.0 DELIVERABLES

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY OR SERVICES

SECTION VI

6.0 GENERAL INFORMATION

6.1 Scheduling Concerns

6.2 Emergency Operations/Mission Essential Personnel

6.3 Contractor Manpower Reporting Application (CMRA) SAM.gov:

6.4 Security Instructions

6.5 Travel

6.6 Employee Accountability & Turnover

6.7 Miscellaneous Paragraphs

SECTION VII

APPENDIX 1

1.0 DEFINITIONS, ABBREVIATIONS, AND ACRONYMS

2.0 ACRONYMS

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General. The Headquarters United States Air Force Director of Air Force Office of Manpower, Personnel and Services, AF/A1X (Directorate of Plans & Integration) is responsible for the Air Force Leadership Development Information Technology (AFLDP IT) platform.

MyVector is an IT (Information Technology) solution currently providing users access to a variety of HR related applications, including: MyVector, Talent Marketplace and the Senior Leader Career Management System (SLCMS) / MAJCOM Senior Leader Management System (MSLMS).

1.1.1 Scope. The AFLDP IT platform serves as one of four (4) current systems used to implement the Air Force A1 Human Resource Information System (HRIS) vision for Force Development (FD). The contractor shall provide support for all aspects of FD within the Department of the Air Force (DAF) and integrate with each of the other three (3) systems to provide a consolidated approach for both the integration and technical sustainment of the platform. The integration and sustainment components shall work in conjunction with the cloud hosting services provided through the Air Force’s Enterprise Cloud One Solution. The contractor shall provide a full range of IT services to support the development, sustainment, enhancement, and facilitation of the platform, and all capabilities and applications within the platform.

SECTION II

2.0 TASK DESCRIPTIONS

2.1 TASK 1: PLATFORM PROJECT MANAGEMENT SUPPORT

The contractor shall provide all overarching personnel resources (administrative, financial, transition, and managerial) necessary for the support of this PWS.

The contractor shall provide overall portfolio, program and project Management in both the strategic, tactical and operational levels as required within the requirements.

The contractor shall assign a Program Manager (PM) which will serve as the primary interface and point of contact (POC) to the Government program authorities and representatives on technical program/project issues.

The contractor PM shall coordinate and facilitate required communications and all activities necessary to ensure the accomplishment of timely and effective support, in accordance with the requirements contained in this PWS.

2.1.1 SUB TASK 1: CONVENE TECHINCAL STATUS MEETINGS

The contractor shall convene all meetings and conferences to be conducted throughout the entire life of the contract. Agendas, presentations materials, and minutes for each meeting, conference and review shall be prepared and delivered IAW CDRLs B001, B002, and B003, respectively. The meetings, conferences and reviews include but are not limited to:

2.1.1.1 Kick-Off Meeting: The Contractor shall schedule and coordinate a project kick-off meeting no later than (NLT) five (5) calendar days after contract award at the location approved by the Government. The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract.

The Contractor shall provide a Kick-Off Meeting Agenda that will include, but not be limited to, the following:

• Introduction of personnel

• Overview of project tasks

• Review of organization (complexity)

• Schedule (shows major tasks, milestones, and deliverables; planned and actual start and completion dates for each)

• Communication Plan/lines of communication overview (between both

Contractor and Government)

• Discussion of draft Program Management Plan (PMP)

• Travel notification and processes

• Government-furnished information (GFI)

• Security requirements (Building access, badges, Common Access Cards

(CAC))

• Analytical Support Status Accreditation (ASSA) Documentation

• Invoice procedures

• Monthly meeting dates

• Reporting Requirements, e.g. Monthly Status Report (MSR)

• POCs

• Roles and Responsibilities

• Overview of incoming Transition Plan to include process, timeframes, and status

• Prioritization of Contractor activities

• Any initial deliverables

2.1.1.2 Technical Status Meetings: The meeting shall provide an opportunity to discuss and respond to questions and inquiries from stakeholders on corresponding sections of the spend plan that affect those offices, PWS requirements initiatives on the planning of activities per specific time periods, and work with appropriate offices to better define requirements.

2.1.1.3 In Process Reviews (IPR): The contractor shall conduct formal IPRs to be held quarterly. The IPR shall provide a forum for Government review of progress, planning, and issues related to the PWS.

2.1.2 SUB TASK 1: DEVELOP PLANS AND REPORTS

The contractor PM shall develop and deliver the following reports and plans:

2.1.2.1 Monthly Status Report (MSR): The contractor shall briefly summarize, by task, the management and technical work conducted during the month. The contractor shall develop the MSR in accordance with CDRL B004, Monthly Status Report.

2.1.2.2 Program Management Plan (PMP): The contractor shall develop and deliver a draft and final PMP that is based on the contractor’s proposed solution outlining the proposed management approach, the tasks and deliverables necessary to meet the PWS objectives.

The contractor shall develop the PMP IAW CDRL B005, Program Management Plan.

2.1.2.3 Trip Reports: Following each trip, the contractor shall prepare and deliver Trip/After

Action Reports to the COR IAW AFH 33-337 and IAW CDRL B006, Travel/Trip Report.

2.1.2.4 Quality Assurance Plan: The contractor shall employ realistic and substantial methods and monitoring techniques for improving the overall quality of the MyVector HRIS Platform and service suites hosted on the platform. The contractor shall develop and update the Quality Control Program (QCP) quarterly in conjunction with the In Progress Review and IAW CDRL B007, Quality Assurance Plan.

2.1.2.5 Problem Notification Report: The contractor shall notify the AFDW/PK Contracting

Officer (CO) or the Contracting Officer’s Representative (COR), in writing, of any technical, financial, personnel, or general managerial problems encountered throughout the performance of the work outlined in this PWS. The Contractor shall inform the COR of issues or potential issues that might affect the performance within two (2) business days of identifying those issues. Verbal reports shall be followed up by written reports within five (5) business days IAW CDRL B008, Problem Notification Report. CDRL B008 shall include at a minimum:

• Status of Problem

• Impacts of Problem

• Recommended Mitigation Strategies

• Proposed Next Steps

2.1.2.6 Transition-In Plan: the Contractor shall provide a Transition-In Plan at the Kickoff

Meeting; the plan shall facilitate the accomplishment of a seamless transition from the incumbent Contractor (if applicable) and incoming Contractor. The Contractor shall identify how it will coordinate with the incumbent Contractor and Government personnel to transfer knowledge regarding the following and IAW CDRL B00A (Phase-In Transition Plan):

a. Project management processes

b. Points of contact

c. Location of technical and project management documentation

d. Status of ongoing technical initiatives

e. Transition of key personnel

f. Schedules and milestones

g. Actions required of the Government

h. Coordination of IT related programs, issues

2.3.1.1 The Contractor shall also establish and maintain effective communication with the incumbent Contractor and Government personnel for the period of the transition via weekly status meetings per the COR’s direction.

2.3.1.2 Incumbent employees may be interviewed for possible employment by the incoming Contractor; however, the employees will have the first right of refusal.

2.1.2.7 Transition-Out Plan: The Contractor shall provide a Transition-Out Plan NLT than 90 calendar days prior to expiration of the contract. The plan shall detail plans for a seamless transition from the incumbent to and incoming Contractor (if applicable). In addition, the Contractor will continue to accomplish all tasks as outlined in the contract during this period. The Contractor shall identify how it will coordinate with the incoming Contractor and Government personnel to transfer knowledge regarding the following and IAW CDRL B00B (Phase-Out Transition Plan):

a. Project management processes

b. Points of contact

c. Location of technical and project management documentation

d. Status of ongoing technical initiatives

e. Transition of key personnel

f. Schedules and milestones

g. Actions required of the Government

h. Coordination of IT related programs, issues

2.3.1.3 The Contractor shall also establish and maintain effective communication with the incoming Contractor and Government personnel for the period of the transition via weekly status meetings.

2.3.1.4 Current employees under this contract may be interviewed for possible employment by a succeeding Contractor; however, the Contractor will have the first right of refusal. The current Contractor will release any employee who chooses to be employed by a succeeding Contractor. The current Contract will assist by orienting assigned employees of the succeeding Contractor during the last 90 days of the period of this contract, if so, directed by the CO. The Government will make available to such employees existing Government Furnished Property listed under Section V of this PWS. Items that are not accountable, such as desks, chairs, telephones, and other normal office equipment and office supplies during the orientation period, will only be transferred to the incoming Contractor if items were solely purchased by the current Contractor’s company.

2.3.2 The contractor shall utilize industry and academia best-practices and methodologies to ensure all activities are identified, documented, and tracked.

The project will continuously be evaluated and monitored for timely and quality service.

2.2 TASK 2: PLATFORM HELPDESK AND SYSTEM ADMINISTRATION SUPPORT

The contractor shall provide IT support to the platform and applications addressed in this document.

2.1.1 The contractor shall provide daily system operational administration services for the platform applications to include; operations, troubleshooting, transitions, installations, integration, modernization, maintenance, conversions, cutovers, and sustainment of all operational software/web-based applications, functions, and IT components of the platform.

2.1.2 The contractor shall identify and collect end-user performance metrics on each of the platform applications, and work with AF/A1X to identify and recommend an acceptable performance baseline. The contractor will resolve any issues when end-user performance metrics fall below established baseline.

2.1.3 System administration support services shall include:

a. Maintaining an up-to-date listing of user accounts, passwords, software licenses, systems file directories and system documentation and accreditation. (CDRL A005, Software License Requirement Lis) ).

b. Develop and/or maintain database and system configuration diagrams and manuals (CDRL A001, Database Design Description)

c. Adding, changing, or deleting user accounts, passwords, and access rights.

d. Maintaining and troubleshooting distribution lists, key personnel rosters and system access lists (SAL) announcement pages.

e. Developing and posting notifications/announcements.

f. Creating, allocating, monitoring, and restoring data files and space.

g. Operating, troubleshooting, and repairing system software malfunctions.

h. System updates.

i. Data integration and migration.

j. Formatting and updating content information screens and tabs.

k. Monitoring site and page use.

l. Updating and maintaining code for existing platform and services.

m. Data analysis.

n. Implementing and sustaining interfaces with systems of record

o. Tracking users.

p. System testing.

q. Updating and testing new configurations.

r. Troubleshoot, maintain, and manage uploading of content.

s. Provide solutions to operating system problems.

t. Implement methodology for systems capacity planning and reporting.

2.1.4 The contractor shall work with AF/A1X to obtain validation, and review and resolve any issues conflicting with Air Force network (AFNET) policies.

2.1.5 The contractor shall serve as the intermediary between the end-user providing system administration, training for IT, technical support, security, administrative control, and application services for all operational systems.

2.1.6 The contractor shall provide helpdesk support to the platform to include identifying, escalating, resolving and tracking problems. The contractor shall provide daily helpdesk support during normal operating hours (may include drill weekends for Air National Guard personnel). Historically, the helpdesk receives approximately 2,000 calls or emails monthly, which is anticipated to increase with civilian use. The contractor shall provide support to the following helpdesk activities:

a. Update, and track phone calls, emails, and all helpdesk inquiries utilizing the existing system Air Force tracking tools to document trouble calls and requests (CDRL B009, Help Desk Report).

b. Document individual trouble calls, requests, and resolution to include the number of calls/emails, average call resolution time, analyses/type of trouble calls, unresolved trouble tickets, and track and resolve quality of service complaints.

c. Identify and determine the severity of the problem for each trouble call.

d. Assign and dispatch problems with appropriate resources, manage, and track through problem resolution.

e. Provide information, updates, and notifications on the status of systems

(downtime and resolution) to the end-users.

f. Contact manufacturers for software under warranty to streamline problem resolution. Analyze trouble call tickets to determine trends and preventive measures. Identify and troubleshoot system problems due to design and implementation constraints.

g. Identify and implement alternatives to resolve system problems.

h. Provide A1 DTA/DPO a monthly problem report describing the number and scope of the previous month’s problems received by the helpdesk.

2.3 TASK 3: BOARD SUPPORT

The contractor shall provide IT support to various DAF boards (promotion, command screening, force development, other) as required by stakeholder offices (approximately 125 per year).

2.3.1 The contractor shall assist the boards at the following known locations: JBSA Randolph (San Antonio, Texas), Washington D.C. Metro Area (National Capitol Region, NCR); Joint Base Andrews (Maryland) and the Air Reserve Personnel Center (Buckley Air Force Base, Aurora, Colorado).

2.3.2 The contractor shall provide IT in support of visual displays, statistics, rankings, system records, as well as software modification, and report generation as determined by the board president secretariat. Historically, Boards last from one

(1) to four (4) weeks each (active duty) and one (1) to five (5) days (Civilian, Air Force Reserve Command (AFRC) and Air National Guard (ANG)).

2.4 TASK 4: SOFTWARE DEVELOPMENT, IMPROVEMENT AND MODIFICATION

The contractor shall support the development, improvement and modification of application/web-based services, using an agile development approach.

2.3.3 The contractor shall support the development, improvement and modification of HR capabilities (web-based) through a low code IT platform solution (such as Outsystems) with capabilities matching rapid prototyping to facilitate the quantification and tracking of human resources, force development, and experience for officer, civilian, and enlisted Airmen across the Total Force.

2.3.4 The contractor shall develop, improve, and modify overall platform and development capabilities within a Government owned and approved cloud system (such as AVD) to provide Government accessibility and visibility throughout the life of the contract.

2.3.5 The contractor shall provide the operations, administration, development, maintenance, and sustainment support of operational and web-based database and information systems that support all applications and mentoring applications hosted on the platform.

2.3.6 The contractor shall support the following functionalities for all requirements provided by the Government:

a. Identify relevant data sources.

b. Develop, maintain, and/or modify web-based services to enable AF users the ability to quickly and easily identify, access, and sort through (education, training or experience) resources.

c. Map (education, training, or experience) tools to the AF competency model and the AF Institute of Technology / Continuing Education.

d. Match mentors and mentees based on individual preferences and algorithmic methods

e. Develop features to provide data reports and analysis of force development and mentoring programs.

f. Develop features, improvements and maintain the Joint Talent Tracking System

g. Develop features, improvements and maintain the Force Development Web

Portal and SharePoint environment.

h. Development of additional features that are identified during development.

2.3.7 The contractor shall support the overall platform and development of capabilities such as but not limited to:

2.3.7.1 TALENT MARKETPLACE

Total Force Assignments to include Officer & Enlisted Military Personnel Section (MPS) Assignments

2.3.7.2 FORCE ENGAGEMENTS & FINANCIAL LITERACY

a. Financial Readiness and Literacy

b. Training Questionnaires and Checklists

2.3.7.3 FORCE DEVELOPMENT AND MENTORING.

a. Total Force Officer & Enlisted Development Plans and Developmental Education

b. Commander Dashboard Reporting w/ Permission set visibility

c. Support for the Air Force Developmental Education Management System

(AFDEMS)

d. MyVector Mentoring Module

e. Support for all applicable Air Force Boards and continued development & support for the in-Board Scoring Tool

2.5 TASK 5: SOFTWARE IMPLEMENTATION

The contractor shall provide software design, implementation, and integration support, general programming support to implement corrections and enhancement to platform application software, and establish implementation plans for software applications and solutions

2.3.8 The contractor shall provide software design, implementation, and integration support, general programming support to implement corrections and enhancement to platform application software, and establish implementation plans for software applications and solutions. The contractor will ensure that all Enterprise Architecture views are properly supported and updated with each new implementation, in accordance with DoDI 5000.82

a. The implementation plans shall define the following elements IAW CDRL A007, Software Development Process Description Document) :

b. Establishing initial vision and roadmap.

c. Identifying minimum viable produce and additional program increment potential features.

d. Prioritizing the program backlog for planning.

e. Building of release packages.

f. Roll-out procedures.

g. Installation procedures.

h. Incident handling and impediment resolution.

i. Distribution controls to include tools.

j. Storage of software.

k. Release review.

l. Documentation of changes.

m. Fallback/back-out arrangements.

2.3.9 The contractor shall provide software testing on all modifications, improvements, and updates. Software testing is a continuous process that shall be incorporated during each development iteration. the contractor shall ensure the test plans include requirements that address the following in accordance with CDRL A006 (Software Test Plan):

a. Performance.

b. Stress.

c. Usability.

d. Pilot.

2.6 TASK 6: SOFTWARE MAINTENANCE

The contractor shall provide software maintenance, administration, installation, and sustainment to include software fixes, patches, and upgrades for operational software applications.

2.3.10 The contractor shall develop a strategy to plan for the maintenance and release of software applications (CDRL A007, Software Development Process Description Document). The plan shall address the following maintenance issues:

a. Planning and control of software application at time of release.

b. Adding features to the product backlog.

c. Backlog prioritization.

d. Resource planning.

e. Bug identification and fixing.

f. Fault corrections.

g. Minor enhancements.

h. Maintenance of documentation.

i. Emergency changes.

j. Interdependencies with other applications.

k. Interdependencies with other infrastructure.

l. Upgrade strategies.

m. Contractual conditions to include support and upgrades.

n. Periodic sprint reviews and prioritization meetings to ensure business requirements are successfully met. The contractor shall be expected to continually deliver software updates and upgrades on a bi- weekly basis or timeline defined by the government.

o. Risks, internal and external.

p. Security requirements.

2.7 TASK 7: APPLICATION WEBSITE MANAGEMENT AND SUPPORT

The contractor shall manage the application website and modify content as necessary to reflect changes in relevant policy and topics of interest.

2.3.11 The contractor shall update and maintain the application web-presence with mobile accessibility and conduct regular reviews of the application web-presence to keep content up-to-date and ensure compliance with established data integrity standards. The contractor shall ensure compliance with DAF and DoD standards for all web services to ensure data integrity by adopting appropriate procedures that relate to specific networks and restricted information.

2.3.12 The contractor shall provide administrative and technical management of all facets of the web- presence to include:

a. Update and maintain identified application web sites for updates, errors and/or problems that arise.

b. Coordinate with business process owners (BPOs), workflow processes, and update web content to integrate new courses and content.

c. Continually review and update links to ensure all links are up-to-date and current; follow up and resolve issues with BPOs for linked pages.

d. Manage identified application-related announcements on the AF Portal homepage.

e. Provide Tier II help desk support to software related issues, data calls, and

Database Administrator (DBA) tasks, and hosting issues with the 844th Communications Squadron responsible for administrating the AF networks at the Pentagon. On average approximately 45 to 50 calls are received monthly. The contractor shall provide Tier II technical support to troubleshoot and resolve software and database problems to include:

a. Identifying system problems due to design and implementation constraints.

b. Identifying and implementing alternatives to resolve system problems.

c. Working with system design engineers on engineering and designing issues to develop operationally sound implementations.

f. Receive requested additions and deletions, work with BPOs and web site OPRs to ensure conformance with application policy and guidance on web page access. Review and take required actions to add, update or delete.

g. Provide .NET, HTML, XML support.

2.8 TASK 8: INFORMATION ASSURANCE (IA) AND SYSTEM SECURITY SUPPORT

2.3.13 The contractor shall provide technical security support to assist in carrying out responsibilities under the AF Personnel Information System Security Plan (ISSP) documented in the System Security Authorization Agreement (SSAA) for the identified systems and applications.

2.3.14 The contractor shall identify any risk to operations, assets, or individuals that has been determined and documented in the System Security Plan, Risk Assessment, or an equivalent document. (CDRL A002, Contractor’s System Security Plan and Associated Plans of Action).

2.3.15 The contractor shall assist in developing policy and guidance to identify problems and requirements needed to attain an acceptable level of risk and adequately plan for required resources.

2.3.16 The contractor shall identify the potential threats that could exploit information system flaws or weaknesses that have been identified and documented in the System Security Plan, Risk Assessment, or equivalent document; confirm the flaws or weaknesses in the information system that could be exploited by potential threat sources that have been identified and documented in the System Security Plan, Risk Assessment, or equivalent document.

2.3.17 The contractor shall identify the security controls (either planned or implemented) for the information system that have been identified and documented in the System Security Plan or equivalent document.

2.3.18 The contractor shall create required documentation to appropriately meet the Air Force Certification and Accreditation Program (AFCAP) and DoD Risk Management Framework (RMF) requirements.

2.3.19 The contractor shall develop and provide draft security documents; review and update existing security documents; provide security test and evaluation (ST&E) support; and provide technical evaluation support in the evaluation of security products in accordance with (IAW) the following (or any newer versions of these governing documents):

a. DoD 8510.1- M, DITSCAP, 31 July 2000;

b. DoD Directive (DoDD) 8500.01E, Information Assurance (IA)

c. 24 Oct 2002; DoDI 8510.01 Risk Management Framework (RMF) for

DoD Information Technology (IT)

d. 19 July 2022, DoDD 8521.01E Department of Defense Biometrics

e. DoDI 8520.02, Public Key Infrastructure (PKI)

f. Public Key (PK) Enabling, 24 May 2011

g. AFI 33-115v1, Network operations, 24 May 2006

h. AFI33-200, Information Assurance (IA) Management, 23 Dec 2008

i. AFI 33-210, Air Force Certification and Accreditation (C&A) Program, 23

December 2008

j. AFI 33-230 Information Assurance Assessment and Assistance Program, 04 Aug 2004

k. AFPD 33-2, Information Assurance (IA) Program, 03 Aug 2011 for preparation of Certification and Accreditation documents

2.9 TASK 9: TRAINING

The contractor shall provide training on platform applications as required.

2.3.20 In coordination with the government PM, the contractor shall plan and schedule training sessions to include conducting virtual webinars and virtual online training sessions demonstrating the capabilities of the enterprise platform.

2.3.21 The contractor shall develop, update, and post standard operating procedures (SOPs), training manuals, briefings, and user guides to support all users on the identified application software and conduct network training based on developed plans.

2.3.22 The contractor shall develop and update SOPs, training manuals, and user guide templates for review and acceptance by the Government and IAW mutually agreed upon templates identified at the KOM.

SECTION III

3.0 SERVICE SUMMARY

The Contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement and will be assessed on an “Acceptable” or “Unacceptable” basis. These thresholds are critical to mission success.

Performance Objective

PWS

Paragraph Performance Threshold Method of

Surveillance SS-1 Provide user metrics with trend assessment on recurring basis

2.4 (Software Implementation)

Metrics delivered on monthly and quarterly basis (no later than 15 calendar days after the month/quarter end, respectively) with variance calculated and trend analysis conducted on increase/decrease in relation to platform activities

As needed Inspection, Observation and Surveillance will be performed by the

COR.

SS – 2

User Guides are established and updated with each release change

2.8 (Training) User Guides are drafted and/or updated with each release with no more than 2 complaints a month.

Customer complaints (Total Force Airmen w/ Civilians – Submitted up through COR)

SS – 3

Active backlogs are properly entered and updated into the Talent Management Integration Suite (TMIS)

2.3 (Software Development, Improvement and Modification)

Backlogs must be updated within 7 calendar days of the end of each sprint and/or each month, whichever is more frequent. The requirements backlog may not contain more than 2% incorrect or inaccessible lines of information.

Periodic Surveillance (Monthly completed by COR)

SS – 4

Provide resolution to customer needs and agency requirements

2.3 (Software Development, Improvement and Modification)

Provide accurate and timely (within 2 business days) responses 95% of the time, receive no more than 5 valid complaints about service during the month

Periodic Surveillance (Monthly completed by COR)

SS-5

Ensure Government managed Enterprise Architecture (EA) views are updated with applicable changes post sprint release

2.4 (Software Implementati on)

All EA needed changes shall be updated within 45 calendar days of the change with any errors corrected within 3 business days of identification

Random Sampling (Audit will be conducted with A1 Chief Enterprise Architect serving as the lead conductor for the audit when requested)

SS- 6 System Availability

2.2.1 (Platform Helpdesk and System Administratio n Support)

Assure availability within the 3 and a half 9’s service availability standard (99.95% system availability rate/resolution, on average, in 4.3 hours per request in order to support the day-to- day operations of the sponsors/stakeholders.

Periodic Surveillance (Monthly completed by COR)

SECTION IV

4.0 DELIVERABLES

The Contractor shall provide deliverable(s) in a format mutually agreed upon by the Government and the Contractor.

The following enumerated deliverables are not expected to change. Due Date intervals are not expected to change but actual dates may need to be revised depending on actual contract start date. See Attachment _2__ for CDRLs.

CDRL # CDRL Title PWS PARA

B001 MEETING AGENDA 2.1.1 Convene Technical Status Meetings

B002 PRESENTATION MATERIAL 2.1.1 Convene Technical Status Meetings

B003 MEETING MINUTES 2.1.1 Convene Technical Status Meetings

B004 MONTHLY STATUS REPORT 2.1.2.1 Develop Plans and Reports

B005 PROGRAM MANAGEMENT

PLAN

2.1.2.2 Develop Plans and Reports

B006 TRIP REPORTS 2.1.2.3 Develop Plans and Reports

B007 QUALITY ASSURANCE PLAN 2.1.2.4 Develop Plans and Reports

B008 PROBLEM NOTIFICATION

REPORT

2.1.2.5 Develop Plans and Reports

B009 HELP DESK REPORT 2.1.6 Platform Helpdesk and System Support

B00A TRANSITION IN PLAN 2.1.2.6 Develop Plans and Reports

B00B TRANSITION OUT PLAN 2.1.2.7 Develop Plans and Reports

A001 DATABASE DESGIN

DESCRIPTION

2.2.3 System administration support

services

A002 CONTRACTOR’S SYSTEM

SECURITY PLAN AND

ASSOCIATED PLANS OF

ACTION

2.8.5 IA and System Security

A005 SOFTWARE LICENSE

REQUIREMENT LIST

2.2.3 System administration support

services

A006 SOFTWARE TEST PLAN 2.4.4 Software Development, Improvement, and Modification

A007 SOFTWARE DEVELOPMENT

PROCESS DESCRIPTION

DOCUMENT SPDD

2.4 Software Development, Improvement and Modification

2.5.1 Software Implementation

2.6.1 Software Maintenance

A006 TRAINING MATERIALS 2.9 Training

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY OR SERVICES

5.1 Government Furnished Property or Services. GFP will be furnished as needed and shall be handled IAW Federal Acquisition Regulation (FAR) 52.245-1.

5.2 Contractor furnished Property. The Contractor shall furnish all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items necessary to perform services as described in the PWS and associated contract documents, except for those items specified in section 5.1 Government Furnished Property.

5.3 The Contractor shall coordinate with the COR for personnel onboarding (including in-processing and out-processing) actions, to include CAC (Common Access Card), laptop and building access as needed.

SECTION VI

6.0 GENERAL INFORMATION

6.1 Scheduling Concerns.

6.1.1 Hours of Operation. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

6.1.2 Duty Hours: The Contractor shall have access to Government facility five days per week, Monday through Friday, eight hours a day, except when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings, unless otherwise approved. Contractor personnel are expected to conform to customer agency normal operating hours; however, the Contractor may be required access to Government facility outside of duty hours based on the customer agency’s needs. As a baseline, Contractor personnel shall work 8 hours per day, 40 hours per week. Compensatory time arrangements are permissible for temporary spikes in worktime; but overtime pay is prohibited without COR and CO approval.

Federal Holidays shall be observed in accordance with Office of Personnel Management policy.

6.1.3 Core Duty Hours and Base Shutdown/Inclement Weather. Core duty hours are 0800

- 1600, Monday through Friday (excluding federal holidays). The Contractor shall follow guidance of the installation containing their place of performance to determine reporting schedules whether due to a base closure or inclement weather. The website for guidance regarding status of performance for work to be performed in the National Capital Region (NCR) is http://www.opm.gov/status/. For our A1 Hub of Joint Base San Antonio (JBSA), follow base commander guidance found at http://jbsa.mil .

The following Federal holidays are observed by this installation:

a. New Year’s Day

b. Martin Luther King Jr.’s Birthday

c. Presidential Inauguration (Every 4 years)

d. President’s Day

e. Memorial Day

f. Juneteenth

g. Independence Day

h. Labor Day

i. Columbus Day

j. Veterans Day

k. Thanksgiving Day

l. Christmas Day

6.1.4 Place of Performance: The primary place of performance for this PWS is the contractor’s location within the Washington DC metro area/NCR. The contractor will be required to routinely travel to the Pentagon, JB Andrews, and AF locations within 50 miles of the Pentagon (e.g. Arlington, VA (Crystal City), Warrenton, VA). The contractor is subject to travel to Continental United States (CONUS) locations on an as-needed basis to include: JBSA Randolph in San Antonio TX, Washington DC Metro area; Joint Base Andrews, Maryland and the Air Reserve Personnel Center, Buckley Space Force Base, Colorado.

6.2 Emergency Operations/Mission Essential Personnel.

6.2.1 Continuation of Essential Contractor Services During Crisis. All services in this

PWS HAVE NOT been defined or designated as essential services for performance during crisis IAW DFARs 252.237-7023, “Continuation of Essential Contractor Services.”

6.3 Contractor Manpower Reporting Application (CMRA) SAM.gov:

6.3.1 The Contractor shall report all labor hours (including subcontractor labor hours) required for performance of services provided under this contract via SAM.gov. Reporting inputs shall be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported anytime during the FY, all data shall be reported not later than 31 October of each calendar year.

6.3.2 Subcontractor CMRA Input: Prime Contractors are responsible to ensure all subcontractor data is reported. Subcontractors will not be able to enter any data into CMRA, but will enter their information into a Bulk Loader spread sheet available from the AF CMRA helpdesk. Subcontractor shall fill in columns A-C then return it to the AF CMRA helpdesk after it's completed and a technician team will enter the information into

CMRA.

6.3.3 Steps for Submitting a Service Contract Report (SCR)

1. Go to www.sam.gov and log in.

2. Select Entity Registrations and then select Service Contract Reporting.

3. SAM displays your entities which have service contracts and meet the reporting criteria. Select View by entity to see the service contracts for each entity.

4. Next, select Add for the service contract against which you want to create a Service

Contract Report. Each service contract which meets the FAR Subpart 4.1703 reporting thresholds is displayed.

5. You will be taken to the Complete Service Contract Report page. SAM displays the contract details and allows you to report. You are required to enter the following information:

a. Total Amount Invoiced: Total dollar amount invoiced for services performed during the previous Government fiscal year under the contract (this amount should include the prime and any subcontract amount).

b. Prime Contractor Hours Expended: Prime contractor direct labor hours expended on the services performed during the previous Government fiscal year. The amount you enter is automatically divided by 2,080 hours to calculate a Full Time Employee (FTE) equivalent, displayed under the Prime Contractor Hours Expended as Prime Contractor FTEs.

6. Report any required Tier 1 subcontractor information by selecting the Add Tier 1 Subcontract Information button.

7. When you are ready to submit the report, select Submit. This saves your report and returns you to the Select Service Contract page where you can create other SCRs or edit an existing SCR

6.4 Security Instructions

6.4.1 Physical Security. The Contractor shall safeguard all Government property, documents and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this contract. At the end of each workday, all Government facilities, equipment, and materials shall be secured by a Government POC. Contractors are not allowed to secure Government facilities, equipment, and materials.

6.4.2 Access Control. The Contractor shall establish and implement methods of ensuring that no building access instruments issued by the Government are lost, misplaced or used by unauthorized persons. Access codes shall not be shared with any person(s) outside the organization. The Contractor shall control access to all Government provided lock combinations to preclude unauthorized entry. The Contractor is not authorized to record lock combinations without written approval by the Government COR. Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers.

6.4.3 Pass and Identification Items. The Contractor shall ensure the pass and identification items required for contract performance are obtained for employees and non-government owned vehicles.

6.4.4 Retrieving Identification Media. The Contractor shall retrieve all identification media, including vehicle passes, from employees who depart for any reason before the contract expires.

6.4.5 Traffic Laws. The Contractor and its employees shall comply with base traffic regulations.

6.4.6 Weapons, Firearms, and Ammunition. Contractor employees are prohibited from possessing weapons, firearms, or ammunition, on themselves or within their Contractor-owned vehicle or privately-owned vehicle while on Joint Base San Antonio, Joint Base Andrews, the Pentagon or any other military facility.

6.4.7 Communications Security (COMSEC). Contractors may require access to COMSEC information on Air Force installations. The Contractor shall not require a COMSEC account. Access shall be controlled by the sponsoring agency. Access to COMSEC material by personnel is restricted to US citizens holding final US Government clearances. Such information is not releasable to personnel holding only reciprocal clearances. If it is determined the Contractor is required to access COMSEC information, the necessary training information and courses shall be provided by the COR. The DD Form 254 shall give further instructions on safeguarding and managing COMSEC material in a SECRET Facility up the CUI level.

6.4.8 Contractor Identification. While on a Government installation or in a Government office space, All Contractor personnel shall wear the Air Force issued Common Access Card at all times when away from their immediate work area so as to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, Contractor personnel shall identify themselves as a contractor to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractors occupying collocated space with their government program customer should identify their workspace area with their name and company affiliation or as a minimum “Contractor” after name.

6.4.9 Drug, Tobacco, and Alcohol Use Policy. The consumption of alcoholic beverages or illegal drugs by contractor personnel, while on duty, is strictly forbidden. Contractor shall immediately remove any employee who is under the influence of alcohol or drugs.

6.5 Travel

6.5.1 Local Travel. Local travel to attend meetings or events may be required at no cost to the

Government. Travel within the National Capital Region and/or Joint Base San Antonio (JBSA) commuting vicinity is considered a cost of doing business and shall not be separately reimbursed.

6.5.2 CONUS Travel: Prior to travel, the Contractor shall coordinate with, and receive approval from, the COR at least 10 business days prior to trip. Travel request form template will be provided by the COR upon Contractor request.

6.5.3 OCONUS Travel: (e.g., to EUCOM and/or PACOM Area of Responsibility) Prior to travel, the Contractor shall coordinate with, and receive approval from, the COR at least 10 business days prior to trip. Theater Business Clearances shall be obtained, as necessary, prior to travel.

6.5.4 Further guidance for Contractor travel can be found at

https://www.defensetravel.dod.mil/site/faqctr.cfm.

6.6 Employee Accountability & Turnover

6.6.1 Staffing of Contractor Personnel. Contractor shall provide a stable workforce, throughout the duration of the contract, by maintaining a 10% or less employee turnover rate.

6.6.2 List of Employees. The Contractor shall maintain a current listing of employees assigned under this contract and define who are key personnel. The list shall include the employee's name, social security number, and level of security clearance. The list shall be validated and signed by the company Facility Security Officer (FSO) and provided IAW CDRL B005 (Monthly Status Report) to the Contracting Officer, Program Manager, and Servicing Security Activity. An updated listing shall be provided upon request.

6.6.3 Contractor professionalism. The contractor shall:

a. Present a professional appearance and maintain professional demeanor and conduct at all times.

b. Conduct their work assignments IAW project schedules

c. Function effectively and efficiently during extended periods of high pressure and stress.

d. Function as an integral member of a team of highly trained professionals responsible for the safety and security of USAF personnel and resources.

6.7 Miscellaneous Paragraphs.

6.7.1 Freedom of Information Act (FOIA). All official Government records affected by this contract are subject to the provisions of the FOIA (5 U.S.C. 552/DoD 5400.7-R/AF Supplement). Any request received by the Contractor for access/release of information from these records to the public (including Government/Contractor employees acting as private citizens), whether oral or in writing, shall be immediately brought to the attention of the CO for forwarding to the AF/A1X FOIA Manager to ensure proper processing and compliance with the Act.

6.7.2 Controlled Unclassified Information (CUI). The Contractor shall comply with DODD 5400-7, Chapter 4, DoD Freedom of Information Act (FOIA) Program requirements. This regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding material.

6.7.3 Privacy Act. Work on this contract may require that personnel have access to information protected by the Privacy Act. Contractor personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations when handling such information.

6.7.4 Records. All records created and received by the Contractor in the performance of this contract shall be maintained and readily accessible. Records shall remain the property of the Government.

6.7.5 Safety Concerns. The Contractor is solely responsible for compliance with OSHA https://www.defensetravel.dod.mil/site/faqctr.cfm standards for the protection of their employees. The Government is not responsible for ensuring that Contractors comply with “personal” safety requirements that do not present the potential to damage Government resources.

6.7.6 Project Policy. The Contractor shall comply with all industry standards. All work shall be done in accordance with all federal, local, and state laws and regulations.

6.7.7 Inherently Governmental Functions. The Contractor shall not perform inherently Governmental functions as defined in the Federal Acquisition Regulation (FAR) Subpart

7.5 in relation to this PWS.

6.7.8 Ethics. The Contractor shall not employ any person who is an employee of the US Government if employing that person would create a conflict of interest. Additionally, the Contractor shall not employ any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval according to DoDD 5500-7, Joint Ethics Regulation.

6.7.9 Professional Appearance of Workspace. The Contractor shall keep workspace areas neat and orderly and avoid conditions leading to safety violations.

6.7.10 Non-Personal Services. The Government shall not supervise or task Contractor employees in any manner that generates actions of the nature of personal services, or that creates the perception of personal services. It is the responsibility of the Contractor to manage its employees directly and to guard against any actions that are of the nature of personal services, or give the perception of personal services to the Government or to Government personnel. If the Contractor feels that any actions constitute, or are perceived to constitute personal services, it is the Contractor’s responsibility to notify the CO immediately. Non-personal Contractor services shall not be used to perform work of a policy/decision making or management nature.

SECTION VII

APPENDIX 1

1.0 DEFINITIONS, ABBREVIATIONS, AND ACRONYMS

Contracting Officer (CO). The duly appointed Government agent authorized to award or administer contracts. The contracting officer is the only person authorized to contractually obligate the Government.

Contracting Officer’s Representative (COR). Designated and authorized in writing by the contracting officer to perform specific technical or administrative functions.

Defective Service. A service output that does not meet the standard of performance specified in the contract for that service.

Government Furnished Property (GFP). Facilities, equipment, tools, supplies, parts, or any other items furnished for the concessionaire's use by the Government. A full list, if applicable, is in Section V.

Performance Threshold. The minimum performance level of a performance objective required by the Government.

Subcontractor – means one that enters into a contract with a prime Contractor. The Government does not have privity of contract with the subcontractor.

Work Day - The number of hours per day the Contractor provides services in accordance with the contract.

Work Week - Monday through Friday, excluding Federal holidays, unless otherwise specified.

Government-furnished Property – As reflected in FAR 52.245-1, Government-furnished Property “means property in the possession of, or directly acquired by, the Government and subsequently furnished to the Contractor for performance of a contract. Government-furnished property includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. Government-furnished property also includes contractor-acquired property if the contractor-acquired property is a deliverable under a cost contract when accepted by the Government for continued use under the contract

Government Property - means all property owned or leased by the Government. Government property includes both Government-furnished and Contractor-acquired property.