HSCGG3-18-R-PWX700_RFP.pdf

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

1. REQUISITION NUMBER PAGE 1 OF

2. CONTRACT NO. 3. AWARD/EFFECTIVE

DATE

4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE

DATE

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME b. TELEPHONE NUMBER (No collect calls)

8. OFFER DUE DATE/

LOCAL TIME

9. ISSUED BY

13b. RATING

14. METHOD OF SOLICITATION

CODE

15. DELIVER TO 16. ADMINISTERED BY CODE

18a. PAYMENT WILL BE MADE BY CODE17a. CONTRACTOR/

OFFEROR

CODE

FACILITY

CODE

CODE

TELEPHONE NO.

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED

RFQ IFB RFP

SEE ADDENDUM

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Govt. Use Only)

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED

29. AWARD OF CONTRACT: REF. OFFER

DATED . . YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA - FAR (48 CFR) 53.212

10. THIS ACQUISITION IS UNRESTRICTED OR

NAICS:

SIZE STANDARD:

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

SET ASIDE: % FOR:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

8 (A)

EDWOSB

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SMALL BUSINESS

21-16-G36PWX601 310

HSCGG3-18-R-PWX700

Kathy P. Klein 304-264-2566 52301 100

United States Coast Guard 408 Coast Guard Drive Kearneysville WV 25430

52301 United States Coast Guard 408 Coast Guard Drive Kearneysville WV 25430

Commanding Officer CG Finance Center 1430A Kristina Way Chesapeake VA 23326-0624

See attached Sections B through M.

See Schedule

541511

$27.5 Million

07/05/2017

08/17/2017

2:00 PM EDT

52301

United States Coast Guard Operations Systems Center 408 Coast Guard Drive Kearneysville WV 25430

51800

STANDARD FORM 1449 (REV. 2/2012) BACK

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED:

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

40. PAID BY

32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f. TELPHONE NUMBER OF AUTHORZED GOVERNMENT REPRESENTATIVE

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

33. SHIP NUMBER 34. VOUCHER NUMBER 35. AMOUNT VERIFIED

CORRECT FOR

PARTIAL FINAL

37. CHECK NUMBER

38. S/R ACCOUNT NO. 39. S/R VOUCHER NUMBER

36. PAYMENT

COMPLETE PARTIAL FINAL

APLES II REQUEST FOR PROPOSAL No. HSCGG3-18-R-PWX700 Command, Control, Communications, Computers and Information Technology (C4IT) Service Center

SECTION B, Page 1

SECTION B: SUPPLIES OR SERVICES AND PRICES

B.1 Brief Description of Services

This solicitation is for an 8(a) single award IDIQ for application product line enterprise support (APLES) services. APLES II services include the full range of software engineering services required to provide full lifecycle support (including design, implementation, operation, maintenance, and enhancement) for USCG enterprise software applications supporting eleven (11) of the USCG’s statutory missions; Ports, Waterways, and Coastal Security, Drug Interdiction, Aids to Navigation, Search and Rescue, Living Marine Resources, Marine Safety, Defense Readiness, Migrant Interdiction, Marine Environmental Protection, Ice Operations, and Other Law Enforcement.

B.2 Place of Performance

The place of performance will be specified at the task order level, but primarily include the USCG, C4IT Service Center and its detachments. Contractor performance may also take place at other USCG entities with written approval from the Contracting Officer.

B.3 Prices

a. This is an Indefinite Quantity contract as contemplated by FAR 16.504. The Contractor shall be reimbursed by the Government in an amount not less than $10,000 (minimum guarantee) nor more than $400,000,000 (maximum ceiling) for successful performance of this contract.

b. The ordering period of this contract shall be from _____ through _______ (60 months).

c. The Government will issue Task Orders based on the work described in Section C of this contract. Task Orders will be issued as either firm fixed price or time and materials type.

Travel will be included as a separate CLIN on all task orders.

B.5 Advanced Understandings

B.5.1 Labor

The Labor rates proposed by the Offeror will be incorporated into the resulting IDIQ contract.

The contractor shall utilize the incorporated labor rates for all task order proposals. The contractor is encouraged to offer discounts to the incorporated rates for all task order proposals.

Command, Control, Communications, Computers, and Information Technology Service Center (C4ITSC)

Application Product Lines Enterprise Services (APLES II)

Indefinite Delivery, Indefinite Quantity Contract

Performance Work Statement

Section C

July 5, 2017

SECTION C, Page 2

Table of Contents

1. VISION

2. INTRODUCTION

4.1 MISSION

4.2 BACKGROUND

3. SCOPE

4. GENERAL REQUIREMENTS

4.1 NON-PERSONAL SERVICES

4.2 BUSINESS RELATIONS

4.3 CONTRACT ADMINISTRATION AND MANAGEMENT

5 PERFORMANCE REQUIREMENTS

5.1 ESTABLISH AND MAINTAIN AN ENTERPRISE AGILE SOFTWARE DEVELOPMENT CAPABILITY

5.2 MAINTAIN AND ENHANCE THE USEFULNESS OF ENTERPRISE INFORMATION SYSTEMS

5.3 MAINTAIN AND ENHANCE THE INFORMATION SECURITY OF ENTERPRISE INFORMATION SYSTEMS

5.4 MAINTAIN AND ENHANCE THE RELIABILITY OF ENTERPRISE INFORMATION SYSTEMS

5.5 MAINTAIN AND ENHANCE THE AFFORDABILITY OF ENTERPRISE INFORMATION SYSTEMS

6 SPECIAL REQUIREMENTS

6.1 SECURITY

6.2 TRANSITION

6.3 GOVERNMENT AND CONTRACTOR FURNISHED RESOURCES

6.4 APPLICABLE DIRECTIVES

6.5 QUALITY

APPENDIX 1 – LABOR CATEGORIES AND DESCRIPTIONS

APPENDIX 2 – DEFINITIONS

APPENDIX 3 – DELIVERABLE DESCRIPTIONS

SECTION C, Page 3

1. Vision

APLES II will provide the United States Coast Guard (USCG) with high productivity Agile software engineering and Operations and Maintenance (O&M) services that will help move the Command, Control, Communications, Computers, and Information Technology Service Center (C4ITSC) towards its envisioned state of technologically innovative, state-of-the-art, electronic and customer centric architecture to support the USCG’s mission.

2. Introduction

The APLES II Contractor will be part of an ecosystem, participating with federal employees and other Contractors in a team based Agile approach to deliver mission value frequently, cost effectively, responsively, and with high quality.

The APLES II Contractor will be expected to work with the current technical architecture and design specified by the Government, and to work within the DHS Agile Development and Delivery for Information Technology and DHS Systems Engineering Life Cycle (SELC) frameworks defined by the Government.

4.1 Mission

The USCG C4ITSC develops, deploys, maintains, operates, and provides user support for USCG Enterprise Information Systems (EIS) in order to improve mission effectiveness through the application of technology.

4.2 Background

The C4ITSC is comprised of the following three (3) partner Centers of Excellence (COEs):

• Operations Systems Center (OSC): Responsible for providing hosting and full life cycle support for operationally focused USCG EIS and critical infrastructure services and components.

• Telecommunications Information Systems Command (TISCOM): Responsible for developing, enhancing and maintaining enterprise IT infrastructure services (including networks, desktop images, embedded devices, etc.) utilized across the Coast Guard, including the cutter fleet.

• Command, Control and Communications Engineering Center (C3CEN):

Responsible for developing, enhancing and maintaining IT Command and Control capabilities and services, including IT systems and electronics.

A primary mission of the C4ITSC is to unify the Coast Guard’s information technology support structure and business practices into a single mission support model.

SECTION C, Page 4

3. Scope

This Performance Work Statement (PWS) describes the requirements and standards necessary to support Department of Homeland Security (DHS) and United States Coast Guard (USCG) Enterprise Information Systems (EIS) developed and/or maintained by the USCG COEs and their detachments

This PWS requires software development and Operations and Maintenance (O&M) service necessary for full lifecycle support for all current and future DHS and USCG EIS developed and maintained by the COEs and their detachments. Support services required by this PWS shall include all solutions, processes, and procedures necessary to sustain EIS at the highest levels of service and availability consistent with cost, schedule, and performance requirements as described in Section 5.0 – Performance Requirements. These services shall include: Program Management support, Business Services, Enterprise Architecture, Application Development and Quality Assurance, Application Maintenance and Support, Application and Data Integration, Data Management, Enterprise Testing and Training, Asset Management, Security and Risk Management, and Technology Services and will be specified in more detail in the PWS for each TO request for proposals/quotations.

Services shall only be provided in response to awarded TO. The Contractor shall fulfill the requirements specified within each TO by executing the requirements (Section 5.0 – Performance Requirements) at the relevant Performance Standards and Acceptable Quality Levels (AQLs) specified in this IDIQ PWS. Each TO PWS will provide the list of requisite deliverables and specify the quantity, frequency, and relevant IDIQ PWS requirements associated with the required services. Descriptions of each type of deliverable and the related requirements are specified in this IDIQ PWS and its appendices.

The USCG currently has IT applications and services that are developed and supported outside of the direct control of the CIO and the C4ITSC. We have initiated an effort to bring all IT under appropriate CIO oversight, and anticipate that through the course of this contract there may be follow-on TO’s to move those applications and services to the OSC and/or take over development and support of those applications and services, within the ceiling of the contract.

This data center and IT systems consolidation effort is directed across the enterprise, and includes consideration of applications supporting all five Coast Guard strategic missions:

Protection of Natural Resources, National Defense, Maritime Safety, Mobility, and Security.

4. General Requirements

This section describes the general requirements for the IDIQ contract and all issued TOs.

4.1 Non-Personal Services

The Government shall neither supervise Contractor employees nor control the method by which the Contractor performs the required work under any TOs issued under this IDIQ contract. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual Contractor employees. It shall be the responsibility of the Contractor to manage its employees

SECTION C, Page 5 and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the Contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor's responsibility to notify the Contracting Officer's Representative (COR) and/or Contracting Officer (KO) immediately.

4.2 Business Relations

The Contractor shall successfully integrate and coordinate all activities necessary to execute the requirements stipulated in any issued TOs. The Contractor shall manage the timeliness, completeness, and quality of services and deliverables. The Contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors.

Deliverables

• Associate Contractor Agreements

4.3 Contract Administration and Management

The following sub-sections specify requirements for contract management, and personnel administration. Contract management and personnel administration requirements and associated deliverables identified in Section 4.3 – Contract Administration and Management and its subsections shall apply to all issued TOs.

4.3.1 Contract Management

The Contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. The Contractor must maintain continuity between the support operations at the C4ITSC COEs and their detachments and the Contractor's corporate offices.

Deliverables

• Contractor Organization Chart

4.3.2 Key Personnel

The Contract Program Manager (CPM), Alternate Contract Program Manager (ACPM), Project Manager(s), and Financial Analyst labor categories shall be considered key personnel. The Contractor shall designate a single CPM and ACPM from among the identified key personnel labor categories who shall be responsible for the performance of the IDIQ contract management and work specified for all issued TOs. The CPM and ACPM shall have full authority to act on behalf of the Contractor for all issues pertaining to the contract administration for APLES II.

The CPM and ACPM shall be available at the primary place of performance identified in the applicable task order during normal working hours or within two (2) hours to meet with

SECTION C, Page 6

Government personnel designated as the KO and/or COR to discuss problem areas. The CMP and ACPM must be able to read, write, speak and understand English.

In addition to the labor categories identified as “Key Personnel” by the Government, the Offeror shall designate any labor categories that are Key to the technical and management performance of the IDIQ/TO effort. The Contractor shall notify the COR and/or KO not less than 30 business days in advance of replacing designated key personnel. The Contractor shall submit written justification for replacement and provide the name and qualifications of any proposed substitute(s). All proposed substitutes shall possess qualifications equal to or superior to those of the key person being replaced and must be approved in writing by the KO. The Government may approve the designation of additional key personnel.

4.3.3 Key Personnel Meetings

The Contractor’s CPM and/or ACPM shall meet with the Government twice monthly to discuss TO progress, exchange information and resolve emergent technical problems and issues. This meeting shall take place at the primary place of performance identified in the applicable task order. Attendees shall include the KO, COR, CPM and/or ACPM, and other Contractor and Government staff as appropriate or requested by the KO. The Contractor shall develop and maintain meeting agendas and minutes documenting topics, decisions, and action items discussed.

Deliverables

• Key Personnel Meeting Agendas and Minutes

4.3.4 Contract Administration

The Contractor shall establish processes and assign appropriate resources to effectively administer the requirements described in this PWS. The Contractor shall respond to Government requests for contractual actions within four (4) business days. The Contractor shall assign work efforts and maintain proper and accurate time keeping records of personnel assigned to work on the performance requirements for all issued TOs.

4.3.5 Personnel Administration

The Contractor shall provide training to maintain the currency of their employees to meet the PWS requirements. The Contractor shall make necessary travel arrangements for employees for Government approved travel. The Contractor shall provide the necessary infrastructure to support contract tasks required at other than normal business hours or the primary place of performance. The Contractor shall provide administrative support to employees in a timely fashion (time keeping, leave processing, pay, emergency needs).

The Contractor shall not employ any person who is an employee of the United States Government if that employment would, or would appear to, cause a conflict of interest. The

SECTION C, Page 7

Contractor shall not employ on a part time or full time basis an employee of the USCG, uniformed or civilian, unless the USCG has officially approved that employment.

The Contractor shall ensure that staffing and skill set mix are maintained at levels sufficient to efficiently and effectively meet each TO’s PWS.

Deliverables

• Contractor Staffing Management Report

4.3.6 Subcontract Management

The Contractor shall be responsible for all subcontract management necessary to integrate work performed under the IDIQ PWS and all TO PWSs and shall be responsible and accountable for subcontractor performance. The prime Contractor will manage work distribution to ensure there are no Organizational or Personal Conflicts of Interest (OCI). Contractors may add subcontractors to their team after written approval from the Contracting Officer (KO). Cross teaming with other OSC Contractors or team members is not permitted.

4.3.7 Contractor Personnel, Disciplines, and Specialties

The Contractor shall accomplish the tasks by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience in accordance with the education and experience criteria specified in APPENDIX 1 – IDIQ Labor Categories and Descriptions. All experience and education shall be in a technical field related to the labor category being proposed. Education must be accredited by an accrediting institution recognized by the U.S.

Department of Education. The Contracting Officer(s) (KOs) for individual TOs may grant six month waivers for Levels I and II on a case-by-case basis if it is determined to be in the best interest of the Government. The Contractor shall ensure the appropriate labor categories and respective levels (e.g., Program Manager I, II, or III), and man-hours utilized in the performance of each TO issued will be the lowest price solution.

Deliverables

• Contractor Staffing Education and Experience Report

4.3.8 Location and Hours of Work

The location and hours or work shall be in accordance with the requirements specified in each

TO PWS.

4.3.8.1 After Hours Access

Afterhours access shall be in accordance with the requirements specified in each TO PWS.

SECTION C, Page 8

4.3.9 Travel

Contractor travel may be required to support this TO. All direct travel costs outside of the local commuting area will be reimbursed in accordance with the Federal Acquisition Regulation (FAR) 31.205-46 - Travel Costs. Reimbursement for travel costs shall not include any indirect costs or labor hours. All labor must be reflected under the appropriate labor CLIN.

The Contractor may make use of Interagency Fleet Management System (IFMS) vehicles (aka GSA Fleet Vehicles) as a means of travel. In order to make use of IFMS vehicles, the Contractor must demonstrate to the COR / KO sufficient evidence that the Contractor has obtained motor vehicle liability insurance covering bodily injury and property damage, with minimum limits of liability as follows; $30k per person, $60k per accident, and $25k in property damage.

The Contractor shall be responsible for obtaining COR and KO approval (electronic mail is acceptable) for all reimbursable travel in advance of each travel event.

5 Performance Requirements

The following sub-sections specify the performance duties applicable for all issued TOs under the APLES II IDIQ contract.

5.1 Establish and Maintain an Enterprise Agile Software Development Capability

The current C4ITSC enterprise software development capability is largely predicated upon a Waterfall approach. Recently, The C4ITSC has started piloting five (5) Agile SCRUM teams.

The C4ITSC’s objective, APLES II, is to transition, establish and maintain an Agile capability to accomplish all software engineering and O&M activities.

The Contractor shall provide the methodology, process, and staff to perform Agile development, testing, required security assessments, release packages, and O&M activities. The Government Product Owner will maintain oversight of the Contractor’s performance and will manage the overall portfolio vision and system architecture direction to determine prioritization of capabilities.

5.1.1 The Contractor shall conduct an assessment of current Agile capabilities

The Contractor shall conduct a formal Agile assessment of the workforce (Contractor and Government) to include the following:

• Define the current state of Agile adoption within the organization and determine the readiness for Agile adoption activities.

• Deliver an Agile transformation roadmap to move from the current state to the desired state. The plan shall include tangible steps to transition from the current state to the desired state.

• At a minimum a one (1) full day assessment review with the Government.

SECTION C, Page 9

Performance Standards and Acceptable Quality Levels (AQLs)

a) Standard: The Contractor’s approach and deliverables shall be in alignment with the Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC), DHS Agile Development and Delivery for Information Technology, and recognized industry best practices.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

b) Standard: Deliverables shall be provided on schedule and free of errors in content, spelling and grammar in order to meet the standard Agile coaching and training to the Government.

c) Standard: All project artifacts shall be maintained in accordance with the Contractor’s Government approved Configuration Management Plan (CMP).

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

d) Standard: All project artifacts shall be developed and maintained in electronic format with read/write capability using applications that are compatible with software included in the USCG Standard Workstation Image.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

Deliverables

• Agile Organizational Assessment

• Agile Transformation Roadmap

5.1.2 The Contractor shall provide Agile coaching and training to the Government

The Contractor shall provide program level coaching on Agile principles and practices: Identify appropriate Agile tools, guidelines and metrics to better establish and improve the use of Agile teams. Support should include identifying standards and practices for a program to manage individual Agile teams and standards for individual Agile teams to follow.

As part of recurring Agile team meetings, the Contractor shall facilitate discussions regarding issues with current Agile team(s) and offer counsel on ways to improve project performance.

The Contractor shall thereafter aid in the implementation of the recommended advice with the team(s).

SECTION C, Page 10

The Contractor shall provide on-site certified trainers to provide training on Agile methodologies. The Contractor shall determine the amount of time required to cover the minimum learning objectives specified below:

• Review the differences between Agile delivery and traditional project management.

• Describe the philosophy and framework of Agile development focusing on a shared set of terms, terminology, and roles and responsibilities.

• Examine the principles and practices of Agile project management including Scrum, Canban, and SAFe.

o Benefits of each method.

o Best uses of each method.

o Where they can fit in the organization.

• Understand the challenges of implementing Agile within the working environment and why the success of Agile projects not only depends on the skills and experience of the project team members, including the Government Product Owner roles, but it also depends on the Agile understanding and awareness of all involved in the project.

• Determine what is needed to initiate an Agile project.

• Demonstrate what is involved in planning an Agile project.

• Examine what is involved when executing an Agile project.

• Practice approaches for monitoring and controlling an Agile project.

• Discuss how to implement Agile delivery in any organization.

o Visualizing workflow.

o How to use a Storyboard / Task Board.

o Setting Work In Progress limits.

o Metrics and measurements and how to make them visible.

o Estimating using Story Points.

Performance Standards and Acceptable Quality Levels (AQLs)

a) Standard: The Contractor’s approach and deliverables shall be in alignment with the Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC), DHS Agile Development and Delivery for Information Technology, and recognized industry best practices.

Government.

SECTION C, Page 11

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

d) Standard: All project artifacts shall be developed and maintained in electronic format with read/write capability using applications that are compatible with software included in the USCG Standard Workstation Image.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

e) Standard: At a minimum the learning objectives outlined under Section 5.1.2 of this PWS will be covered.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

f) Standard: An electronic and printed copy of English language training materials shall be made available to all students.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

g) Standard: An aggregate score of 90% will be achieved on the approved Agile Training Evaluation Form.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

Deliverables

• Agile Training Course Materials

• Agile Training Evaluation Form

• Agile Training for Government Personnel

5.1.3 Implementation of Agile development processes and capabilities

Upon Government approval of the Agile Transformation Roadmap, the Contractor shall implement the plan specified in Section 5.1.1 of this PWS.

Performance Standards and Acceptable Quality Levels (AQLs)

a) Standard: The Contractor’s approach and deliverables shall be in alignment with the Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC), DHS Agile Development and Delivery for Information Technology, and recognized industry best practices.

SECTION C, Page 12

Government.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

d) Standard: All project artifacts shall be developed and maintained in electronic format with read/write capability using applications that are compatible with software included in the USCG Standard Workstation Image.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

Deliverables

• Implementation Kickoff Meeting Agenda, Materials, and Minutes

• Updated Library of Tools, Templates, and Documentation

• Strategic Agile Transformation Outcome Report

5.1.4 The Contractor shall track and analyze the enterprise Agile investment

The Contractor shall draft an Agile Investment and Impact Report that describes the actual outcomes of the Government’s Agile program effort to include the outcomes against the approved plan, goals, and objectives. This report will also identify and recommend candidate improvement objectives and activities for each of the projects to support continuation of the Agile effort.

Using an industry proven approach, the Contractor shall review and report on the Agile program and process to determine the current state of Agile maturity within the organization. This review shall at a minimum address the project and program teams; Integrated Program Teams (IPTs);

stakeholders’ involvement; organization, process and organizational structure; and tools at both the project and program levels. The Contractor shall document their findings and the current state of the Agile maturity of the organization. Following the completion of the Agile review and assessment, The Contractor shall draft the Agile Assessment Report that outlines the findings in terms of people, processes, tools, and technology portfolio, to include the

SECTION C, Page 13 identification of strengths, weaknesses, and recommendations for further improvement to the project and program levels.

Performance Standards and Acceptable Quality Levels (AQLs)

a) Standard: The Contractor’s approach and deliverables shall be in alignment with the Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC), DHS Agile Development and Delivery for Information Technology, and recognized industry best practices.

Government.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

d) Standard: All project artifacts shall be developed and maintained in electronic format with read/write capability using applications that are compatible with software included in the USCG Standard Workstation Image.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

Deliverables

• Agile Assessment Report

5.2 Maintain and Enhance the Usefulness of Enterprise Information Systems

One of C4ITSC’s primary objectives is to deliver products and services that enable increased productivity and reduced cost through the strategic use of enterprise information technology.

This includes systems/applications, capabilities and services that are considered to be useful and easy to use.

SECTION C, Page 14

Information Technology usefulness can be quantified by two (2) specific variables, perceived usefulness and perceived ease of use, which are hypothesized to be fundamental determinants of user acceptance. The following are the definitions of the two (2) variables:

Perceived usefulness is defined as "the degree to which a person believes that using a particular system would enhance his/her job performance".

Perceived ease of use, in contrast, refers to "the degree to which a person believes that using a particular system would be free of effort".

5.2.1 The Contractor shall incorporate Human Systems Integration (HSI) principles into systems engineering processes and system design in order to enhance capability and usability, reliability, maintainability, supportability, and safety while minimizing user errors, time spent performing tasks, productivity loss, and training costs.

The Contractor’s requirements management and engineering strategy and service execution deliverables should incorporate practicable aspects of recognized Human Factors Engineering (HFE) standards to include, but not limited to the following; (ISO 10004) Quality Management – Customer Satisfaction – Guidelines for Monitoring and Measuring, ISO 9241) Ergonomics of Human/System Interaction Standards, (NIST 7432) Common Industry Specification for Usability

– Requirements, and Section 508 Accessibility Standards.

For projects that do not qualify for a National Security Exception as determined by DHS Office of Accessible Systems and Technology (OAST), the Contractor shall develop and maintain a Section 508 Electronic and Information Technology (EIT) Accessibility Plan that includes both functional and technical requirements, design, integration, and testing as well as continued operations and support. When practicable and authorized by the KO, a single plan (one of each type) may be utilized as opposed to one for each system.

Performance Standards and Acceptable Quality Levels (AQLs)

a) Standard: The Contractor’s requirements management and engineering strategy and service execution deliverables should incorporate practicable aspects of recognized Human Factors Engineering (HFE) standards to include, but not limited to the following;

(ISO 10004) Quality Management – Customer Satisfaction – Guidelines for Monitoring and Measuring, ISO 9241) Ergonomics of Human/System Interaction Standards, (NIST 7432) Common Industry Specification for Usability – Requirements, and Section 508 Accessibility Standards.

AQL: Maintain a register of performance elements and an annual (calendar year) aggregate of meaningful and measureable metrics that emphasize the performance elements critical to customer satisfaction.

b) Standard: The Contractor's Section 508 Electronic and Information Technology (EIT) Accessibility Plan shall be developed and maintained in accordance with Department of

SECTION C, Page 15

Homeland Security (DHS) Office of Accessible Systems and Technology (OAST) standards.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

Deliverables

• Section 508 Electronic and Information Technology (EIT) Accessibility Plan

5.2.2 The Contractor shall incorporate Requirements and Design Engineering principles into systems engineering processes and system design in order to gather, analyze, specify, verify, validate, and manage stakeholder desired capabilities and characteristics.

Requirements and Design Engineering should focus on the completeness and continuity of the functional, system, and security requirements and transform those baselined requirements into comprehensive, logical, and detailed designs to efficiently and effectively guide development activities.

The Contractor shall develop and maintain requirements based upon their proposed Agile software development methodology (e.g., Agile SCRUM, Lean and Kanban Development, Extreme Programming (XP), Crystal Method, Dynamic Systems Development Method (DSDM), Feature-Driven Development (FDD)). The Contractor shall map their documentation to the following SELC deliverables; Functional Requirements Document (FRD), Requirements Traceability Matrix (RTM), Developmental Test Plan (DTP), Service Reuse Plan (SRP), System Requirements Document (SRD), Logical Design Document (LDD), System Design Document (SDD), Interface Design Document (IDD), Deployment Plan (DP), Contingency Plan (CP), Disaster Recovery Plan (DRP), and Interconnection Security Agreements (ISAs) for all systems and projects within scope of this PWS (including maintenance). When practicable and authorized by the KO, a single plan (one of each type) may be utilized as opposed to one for each system.

Performance Standards and Acceptable Quality Levels (AQLs)

a) Standard: The Contractor's Functional Requirements Document (FRD) shall be developed and maintained in accordance with Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC) standards and Business Analysis Body of Knowledge (BABoK) best practices.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

b) Standard: The Contractor's Requirements Traceability Matrix (RTM) shall be developed and maintained in accordance with Department of Homeland Security (DHS)

SECTION C, Page 16

Systems Engineering Life Cycle (SELC) standards and Business Analysis Body of Knowledge (BABoK) best practices.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

c) Standard: The Contractor's Developmental Test Plan (DTP) shall be developed and maintained in accordance with Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC) standards.

AQL: Unless otherwise approved by the Government, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

d) Standard: The Contractor's Service Reuse Plan (SRP) shall be developed and maintained in accordance with Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC) standards and Business Analysis Body of Knowledge (BABoK) best practices.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

e) Standard: The Contractor's System Requirements Document (SRD) shall be developed and maintained in accordance with Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC) standards and Business Analysis Body of Knowledge (BABoK) best practices.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

f) Standard: The Contractor's Logical Design Document (LDD) shall be developed and maintained in accordance with Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC) standards and Business Analysis Body of Knowledge (BABoK) best practices.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

g) Standard: The Contractor's System Design Document (SDD) shall be developed and maintained in accordance with Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC) standards and Business Analysis Body of Knowledge (BABoK) best practices.

SECTION C, Page 17

h) Standard: The Contractor's Deployment Plan (DP) shall be developed and maintained in accordance with Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC) standards and Business Analysis Body of Knowledge (BABoK) best practices.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

i) Standard: The Contractor's Interface Design Document (IDD) shall be developed and maintained in accordance with the standards outlined within the Deliverables section of this PWS.

AQL: Unless otherwise authorized by the KO, 100% of products developed and maintained by the Contractor shall be compliant.

j) Standard: The Contractor's Contingency Plan (CP) shall be developed and maintained in accordance with Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC) standards.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

k) Standard: The Contractor's Disaster Recovery Plan (DRP) shall be developed and maintained in accordance with Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC) standards.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

l) Standard: The Contractor's Interconnection Security Agreements (ISAs) shall be developed and maintained in accordance with Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC) standards.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

m) Standard: The Contractor shall define and document customer needs and requirements and establish system specifications utilizing the USCG requirements management systems (currently IBM DOORS and System Architect).

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

n) Standard: The Contractor shall define and document all security requirements utilizing the USCG requirements management systems (currently IBM DOORS and System Architect). Examples of these include but are not limited to the following; NIST 800-53

SECTION C, Page 18 controls, Information Assurance Vulnerability Management (IAVM), Security Technical Implementation Guide (STIG) / Security Requirements Guide (SRG), Health Insurance Portability and Accountability Act (HIPAA), Stakeholder, and Business/Mission.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

o) Standard: The Contractor shall ensure that all design documents clearly identify what and where security requirements are incorporated.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

p) Standard: The Contractor shall ensure that all security requirements are identifiable and reportable separate from functional and system requirements.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

q) Standard: All project artifacts shall be maintained in accordance with the Contractor’s Government approved Configuration Management Plan (CMP).

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

r) Standard: All project artifacts shall be developed and maintained in electronic format with read/write capability using applications that are compatible with software included in the USCG Standard Workstation Image.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

s) Standard: The Contractor shall perform all applicable work in accordance with the standards and deliverables associated with this requirement.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

Deliverables

• Functional Requirements Document (FRD)

• Requirements Traceability Matrix (RTM)

• Developmental Test Plan (DTP)

• Service Reuse Plan (SRP)

• Contingency Plan (CP)

• Disaster Recovery Plan (DRP)

SECTION C, Page 19

• System Requirements Document (SRD)

• Logical Design Document (LDD)

• System Design Document (SDD)

• Interface Design Document (IDD)

• Deployment Plan (DP)

• Interconnection Security Agreement (ISA)

5.2.3 The Contractor shall develop and maintain a strategic information asset base that defines the information, and technologies necessary to perform the mission, and the transitional processes for implementing technologies in response to mission needs.

The domain of Enterprise Architecture (EA) includes both business architecture and technical architecture. The C4ITSC is responsible for developing, maintaining and enhancing the technical architecture baseline to support USCG Headquarters developed and defined business architecture.

EA technical architecture includes baseline architecture, target architecture, and a sequencing plan. EAs are essential for evolving information systems, developing new systems, and inserting emerging technologies which optimize mission value. The existence of an EA is federally mandated by the Clinger-Cohen Act, which makes Chief Information Officers responsible for developing, maintaining, and facilitating the implementation of a sound and integrated IT architecture in their organizations. The USCG EA is aligned to the Department of Defense Architecture Framework (DoDAF). The DoDAF is used to document, describe, and develop the baseline architecture, the target architecture, and the sequencing plan. USCG EAs are required to align with the DHS EA. Individual projects are evaluated through the EA Governance process for architectural alignment. The DHS EA target architecture is evolving to a Service Oriented Architecture (SOA).

Depending upon the needs of the individual project, various EA viewpoint artifacts will be required periodically throughout the program lifecycle.

Performance Standards and Acceptable Quality Levels (AQLs)

a) Standard: The Contractor's architecture deliverables shall be developed and maintained in accordance with Department of Defense Architecture Framework (DoDAF) standards.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

b) Standard: The Contractor shall define and document the enterprise architecture utilizing the USCG EA management systems (currently IBM DOORS and System Architect).

SECTION C, Page 20

c) Standard: All project artifacts shall be maintained in accordance with the Contractor’s Government approved Configuration Management Plan (CMP).

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

d) Standard: All project artifacts shall be developed and maintained in electronic format with read/write capability using applications that are compatible with software included in the USCG Standard Workstation Image.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

e) Standard: The Contractor shall perform all applicable work in accordance with the standards and deliverables associated with this requirement.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

Deliverables

• Department of Defense Architecture Framework (DoDAF) Viewpoints

5.3 Maintain and Enhance the Information Security of Enterprise Information Systems

One of C4ITSC’s primary objectives is to deliver products and services that ensure the appropriate level of protection of the integrity, availability, authenticity, non-repudiation, and confidentiality of enterprise information systems.

5.3.1 The Contractor shall ensure that all technologies within the scope of this PWS and its deliverables remain compliant with the identified information assurance standards.

The Contractor shall employ system security engineering practices guided by NIST 800-160 (series) in the deployment and maintenance of systems to ensure that they are free from conditions that can cause degradation in Confidentiality, Integrity, or Availability (CIA).

The APLES II Contractor shall be responsible for collaborating with the appropriate support service Contractors to ensure that the proper measures are in place that shields technology, components, and information from compromise through the cost-effective application of countermeasures throughout the life cycle of the systems within scope of this PWS.

The Contractor shall develop and maintain a Privacy Threshold Analysis (PTA) and Plan of Action and Milestones (POA&M) for all systems and projects within scope of this PWS. When practicable and authorized by the KO, a single plan (one of each type) may be utilized as opposed to one for each system.

SECTION C, Page 21

Performance Standards and Acceptable Quality Levels (AQLs)

a) Standard: The Contractor's Privacy Threshold Analysis (PTA) shall be developed and maintained in accordance with Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC) standards.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

b) Standard: The Contractor's Plan of Actions and Milestones (POA&M) shall be developed and maintained in accordance with Department of Homeland Security (DHS) Systems Engineering Life Cycle (SELC) standards.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

c) Standard: The Contractor shall maintain a centralized and searchable Plan of Actions and Milestones (POA&M) repository for all systems within scope of this PWS and its deliverables.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

d) Standard: The Contractor shall document and maintain all Plan of Actions and Milestones (POA&M) in the Government sanctioned repository for all systems within scope of this PWS and its deliverables.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

e) Standard: The Contractor shall collaborate with Government and Contractor personnel representing the Information Assurance (IA) domain as part of the development of FIPS- 199 Security Categorization for all systems within scope of this PWS and its deliverables.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

f) Standard: The Contractor shall collaborate with Government and Contractor personnel representing the Information Assurance (IA) domain as part of the development of a System Security Plan (SSP) for all systems within scope of this PWS and its deliverables.

AQL: Unless otherwise authorized by the KO, 100% of new and updated products developed and maintained by the Contractor shall be compliant.

g)…