PIEE RFP - Draft RFP SP4701-20-R-0023.pdf

Procurement Integrated Enterprise Environment Common Operation Environment

SP4701-20-F-0013

Continuation of SF33 A.1 Blocks 8 and 9

Offer must be submitted on or before June X, 2020 (will be update once DRAFT is removed) at 5:00 PM Eastern Time.

The proposal should be emailed (zip file format) to: Contracting Officer Heather Orlando @ email heather.orlando@dla.mil

Note: Facsimile offers are not acceptable forms of transmission for submission of initial proposals or revisions to initial proposals submitted in response to this solicitation. As directed by the Contracting Officer, facsimile may be used during discussions/negotiations, if discussions/negotiations are held, for proposal revision(s), including Final Proposal revision(s).

For questions or concerns regarding this solicitation, please submit your questions by no later than May X, 2020 (will be update once DRAFT is removed @ 2:00pm Eastern Time to Heather Orlando at Heather.Orlando@dla.mil and 215-737-5844. Email is the preferred method of communication.

PLEASE SEE BELOW REMINDERS

Number Reminder Check 1 Fill in and sign SF33 as required?

2 Sign and return any/all amendments?

3 Return one (1) completed copy of the solicitation?

4 Prepare and return electronic copy of the entire Proposal?

5 Submit your best offer?

6 Submit a Small Business Subcontracting Plan if your firm is a large business?

7 Check your math for accuracy on your Price Proposal?

8 Identify your authorized negotiators on page 3 as required? Did you identify which negotiator will serve as the primary point of contact?

9 In accordance with FAR 3.104-4, your company is required to mark all material that may be Source Selection Information, refer to Section L for additional information

CAUTION - CONTRACTOR CODE OF BUSINESS ETHICS (FEB 2012)

FAR Part 3.1002(a) requires all government Contractors to conduct themselves with the highest degree of integrity and honesty. Contractors should have a written code of business ethics and conduct within thirty days of award. To promote compliance with such code of business ethics and conduct, Contractors should have an employee business ethics and compliance training program that facilitates timely discovery and disclosure of improper conduct in connection with government contracts and ensures corrective measures are promptly instituted and carried out. A Contractor may be suspended and/or debarred for knowing failure by a principal to timely disclose to the government, in connection with the award, performance, or closeout of a government contract performed by the Contractor or a subcontract awarded there under, credible evidence of a violation of federal criminal law involving fraud, conflict of interest, bribery, or gratuity violations found in title 18 of the United States Code or a violation of the False Claims Act. (31 U.S.C. 3729-3733) mailto:Heather.Orlando@dla.mil

If this solicitation or contract includes FAR clause 52.203-13 - CONTRACTOR CODE OF BUSINESS ETHICS AND CONDUCT; the Contractor shall comply with the terms of the clause and have a written code of business ethics and conduct; exercise due diligence to prevent and detect criminal conduct;

promote ethical conduct and a commitment to compliance with the law within their organization; and timely report any violations of federal criminal law involving fraud, conflict of interest, bribery or gratuity violations found in title 18 of the United States Code or any violations of the False Claims Act. (31 U.S.C.

3729-3733) When FAR 52.203-13 is included in the contract, Contractors must provide a copy of its written code of business ethics and conduct to the contracting officer upon request by the contracting officer.

SECTION B: SUPPLIES or SERVICE and PRICES/COSTS

The offeror shall use the following tables for the breakout in pricing via Contract Line Item Numbers (CLIN). (See Section L for Pricing Instructions)

FFP = Firm Fixed Price IF = Incentive Fee

Pricing for the Procurement Integrated Enterprise Environment (PIEE ) Common Operating Environment (COE) Support Services* effort includes pricing for Contractor Team Arrangements (CTAs) where Indefinite Delivery Indefinite Quantity (IDIQ) Contracts will be individually awarded to the Team Lead and each of its Teaming Partner(s). Proposed prices include pricing for Program Management Support, Sustainment Services, System Enhancements/Development and the initial Systems Enhancements and Development Task Order, and pricing for the IDIQ Rough Order of Magnitude Tables.

BASE YEAR

CLIN Contract Type Description Unit Unit Cost QTY Target/Estimated

Cost or Fee CLIN 0001 FFP Task Area 1: Program Management Support MO $ 12 $ CLIN 0002 FFP Task Area 2: Sustainment Services MO $ 12 $

CLIN 0003 FFP Task Area 2.1: Sustainment Services – Electronic Document Access MO $ 12 $

CLIN 0004 FFP Task Area 2.2: Sustainment Services – Single Sign On MO $ 12 $

CLIN 0005 Cost Task Area 3: System Enhancements/Development MO $ 12 $

CLIN 0006 IF

Incentive Fee*

System Enhancements/Development

CLIN 000601 IF Incentive Fee Minimum (3% of Target Cost) $ CLIN 000602 IF Incentive Fee Target (offeror to propose) $ CLIN 000603 IF Incentive Fee Maximum (9% of Target Cost) $ CLIN 0007 Cost Travel** LT 1 $100,000.00 CLIN 0008 FFP Other Direct Costs (Hardware/Software) LT 1 $ Total Evaluated Value Base Year $

(*) INFCENTIVE FEE AMOUNTS WILL BE PROVIDED ON EACH TASK ORDER

(**) REPRESENTS A NOT TO EXCEED (NTE) VALUE.

OPTION YEAR 1

CLIN Contract Type Description Unit Unit Cost QTY Target/Estimated

Cost or Fee CLIN 1001 FFP Task Area 1: Program Management Support MO $ 12 $ CLIN 1002 FFP Task Area 2: Sustainment Services MO $ 12 $

CLIN 1003 FFP

Task Area 2.1: Sustainment Services – Electronic Document Access (Optional Task)*

MO $ 12 $

CLIN 1004 FFP Task Area 2.2: Sustainment Services – Single Sign On (Optional Task)* MO $ 12 $

CLIN 1005 Cost Task Area 3: System Enhancements/Development MO $ 12 $

CLIN 1006 IF

Incentive Fee**

CLIN 100601 IF Incentive Fee Minimum (3% of Target Cost) $ CLIN 100602 IF Incentive Fee Target (offeror to propose) $ CLIN 100603 IF Incentive Fee Maximum (9% of Target Cost) $ CLIN 1007 Cost Travel*** LT 1 $100,000.00 CLIN 1008 FFP Other Direct Costs (Hardware/Software) LT 1 $ Total Evaluated Value Base Year $

(*) TASKS BECOME OPTIONAL TASKS IN OPTION YEARS 1 AND 2

(**) INFCENTIVE FEE AMOUNTS WILL BE PROVIDED ON EACH TASK ORDER

(***) REPRESENTS A NOT TO EXCEED (NTE) VALUE.

OPTION YEAR 2

Type Description Unit Unit Cost QTY Target/Estimated

Cost or Fee CLIN 2001 FFP Task Area 1: Program Management Support MO $ 12 $ CLIN 2002 FFP Task Area 2: Sustainment Services MO $ 12 $

CLIN 2003 FFP

Task Area 2.1: Sustainment Services – Electronic Document Access (Optional Task)*

MO $ 12 $

CLIN 2004 FFP Task Area 2.2: Sustainment Services – Single Sign On (Optional Task)* MO $ 12 $

CLIN 2005 Cost Task Area 3: System Enhancements/Development MO $ 12 $

CLIN 2006 IF

Incentive Fee**

CLIN 200601 IF Incentive Fee Minimum (3% of Target Cost) $ CLIN 200602 IF Incentive Fee Target (offeror to propose) $ CLIN 200603 IF Incentive Fee Maximum (9% of Target Cost) $ CLIN 2007 Cost Travel*** LT 1 $100,000.00 CLIN 2008 FFP Other Direct Costs (Hardware/Software) LT 1 $ Total Evaluated Value Base Year $

(*) TASKS BECOME OPTIONAL TASKS IN OPTION YEARS 1 AND 2

(**) INFCENTIVE FEE AMOUNTS WILL BE PROVIDED ON EACH TASK ORDER

(***) REPRESENTS A NOT TO EXCEED (NTE) VALUE.

Type Description Unit Unit Cost QTY Total Price

CLIN 2009 FFP Task Area 4: - Optional Transition-Out Task (3 Months) MO $ 12 $

TOTAL PROPOSED EVALUATED VALUE (TOTAL EVALUATED VALUE BASE

YEAR + TOTAL EVALUATED VALUE OPTION YEAR 1 + TOTAL EVALUATED

VALUE OPTION YEAR 2 + CLIN 2009)

NOTE: The Incentive Fee Maximum will be used for evaluation purposes in determining the overall price of the offerors proposal.

Task Area 2: Sustainment EDA and Sustainment SSO become Optional Task Areas in both Option Year 1 and Option Year 2. If required during the Option Years, these tasks will be included in the Sustainment Task Order at the established prices upon award. Contractors shall submit firm fixed prices for these Optional Tasks in accordance with the above tables.

At time of submittal, the Offeror shall provide prices for the initial Development Task Order (TO) in a accordance with the (PWS) listed in Attachment 1. The Initial Development Task Order shall be used for evaluation of the Offerors ability to support the Offerors technical solution and cost elements. All subsequent Development efforts will be awarded as CPIF TOs under the IDIQ. The PMO anticipates issuance of the first System/Enhancements and Development CPIF TO approximately two weeks after IDIQ award.

Initial Development TO: Systems Enhancements and Development (see Attachment 1 PWS), shall be a Cost Plus Incentive Fee (CPIF). The period of performance for this TO shall be Twelve Months.

Initial Development Task Order Pricing:

CLIN Contract Type Description Unit Unit Cost QTY Target/Estimated

Cost or Fee CLIN 0005 Cost System Enhancements/Development Mo $ 12 $

CLIN 0006 IF

Incentive Fee

CLIN 000601 IF Incentive Fee Minimum (3% of Target Cost) $ CLIN 000602 IF Incentive Fee Target (offeror to propose) $ CLIN 000603 IF Incentive Fee Maximum (9% of Target Cost) $ CLIN 0007 Cost Travel (NTE) LT 1 $100,000.00 CLIN 0008 FFP Other Direct Costs (Hardware/Software) LT 1 $ Total Evaluated Value Base Period

(CLIN 0005 + CLIN 000603 + CLIN 0007 + CLIN 0008)

B.1 General Information:

The PIEE COE Support Services seeks to establish a Contractor Team Arrangement (CTA) approach where Indefinite Delivery Indefinite Quantity (IDIQ) Contracts will be individually awarded to the Team Lead and to each Teaming Partner(s) proposed to perform on the effort. The resultant IDIQ(s) will provide for both Cost Plus Incentive Fee (CPIF) and Firm Fixed Price (FFP) Task Order(s) (TOs) for a three (3) Year Performance Period which includes a one (1) Year Base, and two (2) one (1) Year Options.

Beginning Fiscal Year 2020, the Department of Defense no longer requires contractors to report into the Enterprise-wide Contractor Manpower Reporting Application (ECMRA); instead, Contractors are required to report manpower data relating to the performance of services contracts into the System for Award Management (www.sam.gov), consistent with existing service contract reporting requirements under the Federal Acquisition Regulation (FAR) that currently apply only to Federal civilian agencies. The new initiative will allow industry to report all manpower data into a single Federal-wide portal, removing duplicative requirements; one for DoD and another for the rest of the Federal Government, which require the same data elements to be reported from industry for services contracts performed for both DoD and Federal civilian agencies that essentially perform the same function. The outcome will be a process that is less burdensome on both industry and Government, while improving data integrity and accuracy.

B.2 Indefinite Delivery Indefinite Quantity (IDIQ) Contracts:

This acquisition is structured as a CTA approach where IDIQ Contracts will be individually awarded to the Team Lead and to each Teaming Partner(s) proposed to perform on the effort. The Team Lead will also be required to submit its CTA approach as well as provide a copy of its CTA Document for each Team Partner(s) proposed with its offer.

The IDIQ Contract minimum under the resultant contract is $4M and covers the entire period of the IDIQ contract (One Year Base and Two – One Year Options, if exercised).

The $4M minimum shall be allocated by the Government amongst the CTA (Team Lead and the Teaming Partner(s)) for FFP Task Orders and requires the Team Lead to allocate a minimum of 40% to the small business Teaming Partner(s).

The maximum value of the resultant contract (One Year Base, Two – One Year Options, and Three Month Transition-Out) will be based upon the resultant awardees’ total acquisition price.

B.2.1 Pricing of Task Orders

At time of IDIQ award, Sustainment efforts will be awarded firm fixed price for the base year. The TO will include the Time and Material (TM) Travel Not To Exceed (NTE) Contract Line Item Number (CLIN). The Team Lead will be required to propose a CTA approach where a minimum of 40 percent of the total sustainment price (base and option years) proposed is allocated for Small Business (SB) firms.

Since the IDIQs will be CTAs, individual TOs will be issued to the Team Lead and to each Teaming Partner(s) proposed to perform on the required task.

The Initial Development Task Order shall be used for evaluation of the Offerors ability to support the Offerors technical solution and cost elements. All sequent Development efforts will be awarded as CPIF TOs under the IDIQ. The PMO anticipates issuance of the first System/Enhancements and Development CPIF TO approximately two weeks after IDIQ award.

B 2.2 Rough Order of Magnitude (ROM) Table

Offerors are to utilize the below historical tables (encompass both sustainment and development hours) to establish firm fixed prices (fully burdened) that may be utilized for subsequent task orders for unknown future support. The labor categories listed below shall only be utilized for subsequent task orders.

IDIQ ROM

IDIQ Base Year

Labor Category Estimated Labor Hours

Offeror’s Hourly Labor

Rate

Total Value

Program Manager (Senior) 288

Project Manager (Senior) 3192

Software Architect 5760 $

Systems Engineer (Senior) 11520 $

Software Engineer (Senior) 5760 $

Quality Control (QC) Analyst (Senior) 8820 $

Web Software Developer (Senior) 8700 $

Database Administrator 4788 $

Documentation Specialist (Senior) 5760 $

IT Systems Solution Architect (Senior) 3840 $

Administrator (Senior) 480 $

Administrator (Associate) 312 $

ERP Business Analyst (Senior) 4860 $

Business Systems Analyst (Senior) 8700 $

Applications Programmer (Senior) 4860 $

Web Designer (Senior) 4860 $

Web Designer (Intermediate) 4860 $

Web Content Administrator 2940 $

Quality Control (QC)Analyst (Intermediate) 8820 $

Web Software Developer (Intermediate 8700 $

Software Engineer (Intermediate) 14700 $

Systems Engineer (Intermediate) 11556 $

Applications Programmer (Intermediate) 10860 $

Total ROM Price for IDIQ Base Year

IDIQ ROM Table IDIQ Option Year 1

Labor Category Estimated Labor Hours

Offeror’s Hourly Labor Rate

Total Value

Program Manager (Senior) 288

Project Manager (Senior) 3100 $

Software Architect 11400 $

Systems Engineer (Senior) 5760 $

Software Engineer (Senior) 5700 $

Quality Control (QC) Analyst (Senior) 8820 $

Web Software Developer (Senior) 17640 $

Database Administrator 4700 $

Documentation Specialist (Senior) 5700 $

IT Systems Solution Architect (Senior) 3800 $

Administrator (Senior) 419 $

Administrator (Associate) 312 $

ERP Business Analyst (Senior) 4860 $

Business Systems Analyst (Senior) 8700 $

Applications Programmer (Senior) 4860 $

Web Designer (Senior) 4860 $

Web Designer (Intermediate) 4860 $

Web Content Administrator 2940 $

Quality Control (QC)Analyst (Intermediate) 8820 $

Web Software Developer (Intermediate 17640 $

Software Engineer (Intermediate) 10860 $

Systems Engineer (Intermediate) 11400 $

Applications Programmer (Intermediate) 10860 $

Total ROM Price for IDIQ Option Year 1 $

IDIQ ROM Table IDIQ Option Year 2

Labor Category Estimated Labor Hours

Offeror’s Hourly Labor Rate

Total Value

Program Manager (Senior) 288

Project Manager (Senior) 3100

Software Architect 5500

Systems Engineer (Senior) 5760 $

Software Engineer (Senior) 11000 $

Quality Control (QC) Analyst (Senior) 8820 $

Web Software Developer (Senior) 17640 $

Database Administrator 4697 $

Documentation Specialist (Senior) 5700 $

IT Systems Solution Architect (Senior) 3799 $

Administrator (Senior) 400 $

Administrator (Associate) 300 $

ERP Business Analyst (Senior) 4860 $

Business Systems Analyst (Senior) 8700 $

Applications Programmer (Senior) 10860 $

Web Designer (Senior) 4860 $

Web Designer (Intermediate) 4860 $

Web Content Administrator 2940 $

Quality Control (QC)Analyst (Intermediate) 8820 $

Web Software Developer (Intermediate 17640 $

Software Engineer (Intermediate) 14700 $

Systems Engineer (Intermediate) 11000 $

Applications Programmer (Intermediate) 10860 $

Total ROM Price for IDIQ Option Year 2 $

B.3 Contractor Team Arrangement:

A Contractor Team Arrangement (CTA) allows for contractors to work together to meet agency requirements and are not established pursuant to FAR Subpart 9.6; instead, contractors will determine the relationship between the various team members, but they will all be primes and not subcontractors. There will be a single leader for the team, which will have overall responsibility for contract performance and will serve as the system integrator for this effort. The team lead will therefore develop and oversee system development and coordinate with other team members in support of Sustainment efforts. Although the proposed approach may result in multiple contract awards, it is being solicited pursuant to FAR 16.5 using a single solicitation, and the resulting award(s) may be to a group of contractors organized as a single team (Contractor Team Arrangement) as described below. Within this acquisition, the DLA Contracting Services Office located at Philadelphia (DCSO-P) requires CTAs with small businesses and encourages CTAs with other firms that could contribute to the success of the PIEE COE Support Services effort. In an attempt to facilitate this process, the following definitions and information are provided with regard to Team Arrangements.

• Contractor Team Arrangement – A Contractor Team Arrangement means an arrangement in which two or more companies form a partnership to act as a potential prime contractor.

• Team Lead – The CTA must designate one (1) team member to be the “Team Lead.” DCSO-P requires that the Team Lead, at a minimum, be responsible for coordinating and overseeing the timeliness and quality of work performed under all Task Order(s) issued to the various Team Partners, and for coordinating the submission of the proposal for the PIEE COE Support Services effort.

• Team Partner(s) – A Team Partner is a firm that is a member of the CTA. Each Team Partner(s) will provide the services identified in the CTA Document in accordance with the team’s proposal and terms of the contract.

• Subcontractors – Subcontractors are firms who provide services on behalf of one or more of the

Teaming Partner(s).

Subcontractors are not considered members of the CTA and responsibility for the subcontractor will rest with the applicable Team Partner. Subcontractors may be large or small businesses and may not be used to satisfy the Small Business (SB) requirement that a minimum of 40 percent of the total sustainment price for the base and option years for the PIEE COE Support Services effort must be dedicated to either a SB, Small Disadvantaged Business (SDB), Women-Owned Small Business (WOSB), Veteran-Owned Small Business (VOSB), Service Disabled Veteran Owned Small Business (SDVOSB), and/or HubZone Small Business (HZSB) concerns.

The Team Lead is fully responsible for contract performance, regardless of any team arrangement between the Team Lead and its Team Partner(s) or subcontractor(s).

B.4 Support of Socio Economic Programs:

The Defense Logistics Agency (DLA) is committed to assuring that maximum practicable opportunity is given to Small Business concerns to participate in this acquisition and shall do via contactor teams.

Therefore, DLA requires that a minimum of 40% of the total dollars proposed for the Sustainment portion of this requirement for the base and option years for the PIEE COE Support Services shall be dedicated to Small Business.

The Team Lead, if a large business, is required to form CTA with at least one (1) small business and at least one (1) other small business category referenced below to satisfy the DLA requirement that a minimum of 40% of the total sustainment price for the base and option years shall be dedicated to Small Business. Each small business teaming partner will receive an individual IDIQ contract award/number.

TYPE OF SMALL BUSINESS

Women-Owned Small Business (WOSB) Service Disabled Veteran-Owned Small Business

(SDVOSB)

Veteran-Owned Small Business (VOSB) Hub Zone Small Business (HZSB) 8(a), Small Disadvantaged Business (SDB)

One (1) firm may fulfill more than one of the socio-economic categories listed above. For example, in addition to being a small business concern, if that business is also a SDVOSB, and 40% of the total sustainment price for the base and option years is dedicated to that business, then that would satisfy the requirement that the Team Lead form the requisite CTAs.

Note: No advantage will be given to a proposal that offers a percent of participation greater than 40 percent of the total sustainment for the base and option years for this acquisition. This requirement is only applicable to Offerors that are other than Small Businesses (SBs) and shall be rated on an Acceptable/Unacceptable basis as part of the Price Proposal Evaluation.

Initial proposals not complying with the socio-economic requirements outlined in this RFP shall be considered unacceptable. The Team Lead has the overall responsibility for the planning, programming, coordination, management, and performance of all services and tasks under the Task Order(s) issued to its Teaming Partner(s), including the quality and timeliness of those tasks, regardless of the allocation of responsibility for those services and tasks in the CTA.

The Team Lead will submit one overall team non-price proposal and one overall team price proposal. The Team Lead will be responsible for coordinating and overseeing all Task Order(s) issued to the Teaming Partner(s), for coordinating the submission of the offer for this RFP and will be responsible for the timeliness and quality of all deliverables for the PIEE COE Support Services effort.

CTA Document: The CTA is required to submit a CTA Document as part of its offer as evidence of the Contractor Team arrangement. The document should designate all team members and describe the tasks to be performed by each team member, along with associated proposed prices. A concern’s size standard at the time of proposal submission will be verified with the System for Award Management (SAM) and/or the Small Business Administration. For the purpose of determining a firm’s size, the applicable North American Industry Classification System (NAICS) code and related small business size standard are 541519 and $30,000,000 respectively.

A Team Arrangement is also encouraged to establish relationships with other small business types in support of the socio-economic programs.

TO BE ELIGIBLE FOR IDIQ AWARD, SIGNED SF33’S FROM THE TEAM LEAD AND EACH

TEAM PARTNER MUST BE SUBMITTED WITH THE OFFEROR’S PROPOSAL (IAW with

ATTAHMENT 2)

• The Team Leader shall submit a consolidated offer referencing what roles and/or taskings each team member will fulfill and the relative cost to be allocated to each team member.

SECTION C

PERFORMANCE WORK STATEMENT (PWS)

C.1 BACKGROUND

The Procurement Integrated Enterprise Environment (PIEE) Common Operation Environment (COE) is the single face system delivering access to a number of independently managed business applications and capabilities. The PIEE COE represents a new Department of Defense (DoD) acquisition strategy of providing procurement business and financial services capability to procurement professionals in support of the war fighter. The PIEE COE is not an individual Information Technology (IT) application or system. Rather, it’s a collaborative COE based on core components designed to present a virtual procurement workspace for professional procurement individuals.

There are many applications that reside in the PIEE COE. The below identifies the applications and their respective capabilities they represent (Requirements, Award, Post- Award Administration, Payment, Property Management, Purchase Card, Security, and Operational Support):

• WAWF (formerly Invoice Receipt Acceptance and Property Transfer (iRAPT)), to include

WAWF mobile applications

• MyInvoice

• Item Unique Identification (IUID) Registry

• Surveillance and Performance Monitoring (SPM)

• Electronic Military Interdepartmental Purchase Request (eMIPR)

• Management Reporting System (MRS)

• National Industrial Security Program (NISP) Contracts Classification System (NCCS)

• Contract Closeout (CCO)

• Contract Deficiency Reports (CDR)

• Contracting Communication (CCM)

• Government Furnished Property (GFP)

• Solicitation

• Joint Appointment Module (JAM)

• Purpose Code Management (PCM)

• Government Purchase Card (GPC)

• Web Based Training (WBT)

• Electronic Data Access (EDA)

• Single Sign On (SSO)

For additional detailed information on all of these capabilities, visit the following link:

https://wawftraining.eb.mil/wbt/ https://wawftraining.eb.mil/wbt/

C.2 CONTRACT SCOPE

The scope of this effort includes ongoing analysis for software design and development, solution integration, testing and deployment, application sustainment, and program management support for the core PIEE COE applications and capabilities including future enhancements.

• The Contractor shall provide development skills to enhance and expand existing capabilities while effectively sustaining the daily operational environments utilized by the agency. This effort includes necessary enhancements to address DoD mandates or required external regulatory updates and continued efforts to meet audit readiness goals.

• The Contractor shall use Agile Development Methodologies (Agile) to support all stages of the Software Development Lifecycle (SDLC). Agile certifications are required for all indicated tasks and shall be indicated on Key personnel resumes, along with actual certification documentation.

• The Contractor shall assess project requirements to determine and provide estimated labor hours per labor category as well as identification of assumptions, risks, potential cross team and cross system impacts.

• The Contractor shall adhere to established DLA Enterprise Change Management (ECM) and Enterprise Architecture processes throughout the Agile SDLC.

• The Contractor shall develop and/or maintain all technical documentation including but not limited to system and database design documentation, and architectural and network diagrams that encapsulates existing and future PIEE applications and capabilities.

• The Contractor shall support transition from the current hosted environments to the PIEE Cloud Computing Environments.

• The contractor shall make architectural and engineering changes to leverage the cloud native capabilities to reduce operational cost and improve performance.

• The Contractor shall provide full system development, management and enhancement support to include system test and evaluation, system and database administration, training, and enhancement of PIEE capabilities identified in Section 1.0.

• The Contractor shall perform security related activities to include, but not limited to resolving Information Assurance Vulnerability Alerts (IAVAs) and other United States Cyber Command (USCYBERCOM) tasks in collaboration with the Program Management Office (PMO), and the Information Assurance Manager (IAM).

• The Contractor shall implement the Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs) and National Institute of Standards and Technology (NIST) and other cyber related compliance activities, and analyze patches issued by Commercial product vendors affecting PIEE operations.

• The Contractor shall use Continuous Integration/Continuous Delivery capability (CI/CD) pipeline and tools to facilitate code being deployed in production and test environments.

• All development of Electronic and Information Technology products or services shall be compliant with Section 508 as imposed by 36 CFR 1194. Solutions implemented by the contractor shall comply with the DLA One-Book DLA Directive 5025.30. When directed by the Government, the Contractor shall assist the Government in performing an assessment of Engineering Changes (EC) to determine compliance with Section 508 and provide results to the Government. The Contractor shall assist the Government in developing a plan to meet these requirements or requesting appropriate exceptions.

• The contractor shall support the Government in its compliance with Section 508 throughout the development and implementation of the work to be performed. Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d) requires that when Federal agencies, develop, procure, maintain, or use electronic information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who do not have disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.

Additional information be found at - http://www.section508.gov

At the direction of the Strategic Capabilities and Processes Office (SC&P) and in conjunction with DLA technical leadership, the contractor shall implement architecture standards and frameworks that include but are not limited to:

• Adoption and use of Open Source Software

• Cloud-based architecture development and enablement

• Compliance with the Service Layered Architecture Profile (SLAP) standards and technology profile for the development and implementation of software within the

PIEE COE

• Implementation and adoption of system interoperability standards that define secure integration patterns for use within DLA, with government partners and commercial and public resources

• Adoption of a single identity and access management solution that is extensible, service based and secure

• Implementation and adoption of common services to address application architecture concerns such as error handling, system logging, audit logging, authentication, authorization, and monitoring and more.

The contract area(s) in scope of the Performance Work Statement (PWS) include the following taskings:

NOTE: This contract is for Internal Use Software (IUS) as defined in Statement of Federal Financial Accounting Standards (SFFAS) Number 10, Accounting for Internal Use Software. Individual IUS-related items of performance or deliverables under this contract are included in specific item numbers. Invoicing for and inspection and acceptance of contract performance and deliverables will be based on each applicable IUS category as a http://www.section508.gov/ separate item in accordance with the IUS capitalization table. Throughout the PWS, tasks are identified with the applicable IUS number, which needs to be included on any invoice.

Task Area 1 – Program Management Support – Firm Fixed Price (FFP) (IUS #0003 Expense)

• Task 1.1 – Kick-off Meeting

• Task 1.2 – Program Management Plan (PMP)/Integrated Master Plan (IMP)

• Task 1.3 – Integrated Master Schedule (IMS)

• Task 1.4 – Quality Control Plan (QCP)

• Task 1.5 – System Engineering

• Task 1.6 – Configuration Control Governance

• Task 1.7 – Configuration Management

• Task 1.8 – Weekly Status Report

• Task 1.9 – Monthly Performance and Progress Report (MPPR)

• Task 1.10 – Standard Operating Procedures

• Task 1.11 – PMO Audit Readiness

• Task 1.12 – Transition-In Plan

• Task 1.13 – Work Breakdown Structure (WBS) and Cost

Task Area 2 – Sustainment Services – Firm Fixed Price (FFP) (IUS #0003 Expense)

• Task 2.1 – EDA Sustainment

• Task 2.2 – SSO Sustainment

• Task 2.3 – System Maintenance

• Task 2.4 – Production and Development Baselines

• Task 2.5 – System Design Documentation

• Task 2.6 – Business Intelligence Reporting

• Task 2.7 – Security Test and Evaluation

• Task 2.8 – Public Key Infrastructure (PKI)/Personal Identity Verification (PIV)

Interoperability Annual Test

• Task 2.9 – Back-up and Continuity of Operations

• Task 2.10 – Application Rollback Strategy

• Task 2.11 – Tier 3 Help Desk Support

• Task 2.12 – Trouble Ticket/Problem Report Resolution – Trouble Ticket Analysis

• Task 2.13 – System Break Fix

Task Area 3 – Systems Enhancements and Development – Cost Plus Fixed Fee (CPFF) (IUS #0002 Capitalize)

• Task 3.1 – System Enhancements o Task 3.1.1 – Requirements Phase

• Task 3.2 – Software Development

• Task 3.3 – Code Development

• Task 3.4 – Interface Identification and Development

• Task 3.5 – Testing

• Task 3.6 – Testing Support

• Task 3.7 – Training

• Task 3.8 – Software Deployment

Task Area 4 –Transition-Out (FFP) (IUS #0003 Expense)

• Task 4.1 – Transition-Out Plan

• Task 4.2 – Transition-Out Implementation

C.3 OBJECTIVE

The PIEE COE provides for the comprehensive development, implementation, transition, operations and support of a number of independently managed business applications and capabilities. This effort must meet evolving requirements for enhancements while leveraging agile best practices in software development including but not limited to open source code, human-center design, and with an extensible infrastructure and robust communication between the stakeholder community and project team. This effort must also be managed in accordance with an integrated master plan that address a number of intersecting and mutually supporting programs that DLA also manages.

C.3 SYSTEM REQUIREMENTS

THE FOLLOWING SYSTEM REQUIREMENTS ARE REQUIRED FOR THIS

EFFORT:

HARDWARE/SOFTWARE:

The contractor shall deploy the systems and Capabilities solution in PIEE COE as identified in Paragraph 1.0., on premise and/or IL-5 GovCloud environments. In addition, the contractor shall support the implementation and maintain each PIEE COE products in all development, test and production environments.

The contractor shall be able to support Operating Systems (OS) and software component such as (but not limited to):

Operating Systems:

• OS: RHEL 7.x, Windows, Solaris 10/11

The software list is as below:

• Hadoop (HDFS) HDP V3.0.1

• HBase 2.0.0.3

• ELasticSearch V 6.6.0 Includes Kibana, X-Pack

• Docker EE V 18.09.1

• NiFi 1.8.0

• ZooKeeper 3.4.9.3

• Ambari Metrics 0.1.0

• AngularJS V 6

• Spring Boot (contains Tomcat) 2.0+

• NGINX (Docker Image) 1.15.8

• Java - Open JDK V 10

• Oracle Enterprise Edition, Oracle RAC V 19C

• Oracle Data Guard for Replication

• Structured Query Language (SQL)

• WebSphere Application Server V 9.x

• Symantec Anti-Virus Engine

• NiFi 1.8.0

• HSM with Luna FE (Safenet)

• SQL Server DB – for Sharepoint

• Informatica

• Windows Server

• AWS Oracle RDS (Multi-AZ) 19C

• AWS KMS (Key Management Service)

PERFORMANCE PARAMETERS:

PIEE COE must meet the following minimum performance objectives:

• Support 550,000 registered users with annual growth rate of 35,000 to 40,000 per year.

• Support 10,000-10,500 average concurrent users with a peak of not more than 12,500 concurrent users.

• Support processing peaks in usage (estimate 20% over normal usage) the last weekend of every month, the first month of October, and for the entire month of September and December.

• Store and archive invoices and receiving reports annually.

• Process a minimum of 132,000,000 transactions with an annual growth rate of 12,000,000 transaction growth.

• Process each real-time data input transaction within five seconds exclusive of network transit.

• Initiate processing of each batch file within one hour of submission.

• Initiate each e-mail notification immediately on processing.

• EDA supports processing a minimum of 9,507,893 documents with an annual growth rate of 6 million documents.

Critical Capabilities:

• Maintain/Provide single login access to PIEE COE and subscribing Service Component and Agency ERP solutions using DoD Common Access Card (CAC);

DoD managed External Certificate Authority (ECA) hardware tokens; JITC certified interoperable Federal Agency Personal Identity Verification (PIV); Non- Federal Agency Public Key Infrastructure (PKI), and Coalition Partner smartcards, and passwords meeting the operative complexity requirements.

• Maintain/provide authorized DoD personnel and authorized industry representatives a single location to access a repository of electronically stored, post-award procurement documents via the Internet. Such as but not limited to the following: personal property and freight Government Bills of Lading (GBL), Government Transportation Request (GTR) and the Contract Deficiency Report (CDR) Workflow capability, Signature Card DD577, Standard Form 44, Non- Automated General Bill of Lading, Contract Warrants, MIPR, and other document types as needed.

• Maintain/Provide role-based permissions access to functional and technical capabilities in PIEE.

• Support Separation or Segregation of Duties (SoD) for key duties.

• Provide support for security-relevant to key application events as required.

• Provide a Service-Oriented Architecture (SOA) approach to data sharing and data collection.

• Provide data-sharing using Extensible Markup Language (XML) format standard and Web Services.

• Apply time stamps to all PIEE COE transactions.

• Upon Government approval, implement role-based permissions to allow visibility and access to PIEE COE situational awareness data and user services delivered in a Common Operating Picture (COP).

• Provide WBT for system users.

• Support web user interactive and asynchronous data services (i.e., Secure File

Transfer Protocol (SFTP), Electronic Data Interchange (EDI), and Web Services).

• Minimize data entry errors by maximizing support for the DoD Information

Sharing and Net- Centric Data Strategies.

• Capture a digital signature of the acceptance of contract performance and other

PIEE COE processes requiring electronic certification.

• Manage all records in accordance with records management policies to include archival, retention and deletion.

• Transmit all audit transaction records daily to DLA approved systems.

• Capability to provide custom reports as requested, and develop canned reports.

• Enable micro-services based flexible and loosely coupled architecture.

C.4 OBJECTIVESPECIFIC TASK REQUIREMENTS

The contractor will be required to perform task such as the following:

(Note: The Government reserves the right to remove tasks during performance if it deems the tasks are no longer required.)

TASK AREA 1 – Program Management Support

Task 1.1 Kick-off Meeting

The Contractor shall schedule a Kick-off Meeting with the PMO and KO within two weeks of award or as agreed upon between the Government and contractor, to introduce the Government team to the contractor’s overall operating plans and approach to this work.

The Contractor shall be prepared to discuss the content of the Program Management Plan/Integrated Master Plan (PMP/IMP), to include the staffing plan, schedule, and proposed metrics. The Contractor shall produce and distribute Kick-off briefing presentation material and Meeting Minutes (CDRL A001) identifying all the discussion points, agreements, and action items following the meeting.

The Contractor shall be responsible to provide the following deliverables:

• Kick-off Briefing Presentation Material and Meeting Minutes (CDRL A001)

Task 1.2 Program Management Plan/Integrated Master Plan (PMP/IMP)

The PMP/IMP (CDRL A002) is a formal, approved document used to manage project execution and project control. It is a management tool for planning, executing and tracking technical, schedule and cost status, including risk mitigation efforts. The PMP/IMP is used to optimize the overall execution strategy of a program, coordinate workflows and assist in the decision-making process. It serves as a foundation for Program Management, cost estimates, budgets, schedule and risk assessments. Program Management activities for this initiative will become a part of the overall documentation prepared and maintained by the PMO. This Task represents the Program Management support required to fulfill the execution of the following Tasks.

The Contractor shall prepare a PMP/IMP (CDRL A002) and provide an update at a minimum quarterly describing the overall approach to the management of this task orders.

At a minimum, the PMP/IMP will describe the following:

• Provide the organizational structure of the Contractor by role and Key Personnel Identification.

• Provide description of how personnel and physical resources will be managed.

• Provide identification of mechanisms to control schedule and performance.

• Document the process and technical approach for Program Management of the Task

Order.

• Document the process and technical approach for the Sustainment of the current system

• Document the agile/scrum process and technical approach for new development/enhancements of capabilities.

• Document risk management process.

The Contractor shall provide the planning, supervision, coordination and controls necessary to accomplish all work contained in this PWS. The Contractor shall document their approach and plan that defines the activities, tools, and techniques to ensure high-quality products that are defect free, that meet PWS requirements by sub-task and that are delivered in accordance with the approved schedule.

• Program Management Plan/Integrated Master Plan (PMP/IMP) (CDRL A002)

Task 1.3 Integrated Master Schedule (IMS)

The IMS (CDRL A003) is a time-based schedule containing the networked, discrete detailed work packages/tasks necessary to ensure successful program/task order execution.

The IMS is traceable to the PMP/IMP, the WBS, and this PWS. The IMS is used to verify attainability of task order objectives, to evaluate progress toward meeting program objectives, and to integrate the program schedule activities with all related components.

The IMS depicts Contract Milestones, Deliverables, individual discrete task, their durations and inter-dependencies. The IMS is a living document that is continuously updated (minimum weekly) to reflect the progress of the program.

The Contractor shall align the IMS and support the PMO by providing needed inputs into the PMOs Master Schedule on a weekly basis.

• Integrated Master Schedule (CDRL A003)

Task 1.4 Quality Control Plan (QCP)

The QCP is developed by the Contractor and is the driver for service quality. The Contractor is required to develop a comprehensive program of inspections and monitoring actions, to include the QCP. The QCP, in conjunction with the QASP, is intended to verify that the Contractor’s quality control program and is intended to provide the measures needed to lead the Contractor to project success. Once the quality control program, to include the QCP, is approved by the Government, careful application of the process and standards presented in the QASP document will ensure a robust quality assurance program. A QCP will be completed by the Contractor and due one (1) month after award of the contract. The Contractor shall report surveillance metrics every month, by the 5th calendar day as part of the MPPR. An updated QCP will be submitted one (1) month after start of optional period of performance.

The Contractor shall deliver to the PMO a draft QCP (CDRL A004) within one month of Award and a final within 10 days after Government review.

• Quality Control Plan (QCP) (CDRL A004)

Task 1.5 Systems Engineering

The Contractor shall integrate the technical efforts related to the design, development, testing, configuration, implementation and deployment of the system baselines and their life cycles. The Contractor shall provide the technical information to support program management to include management of each system configuration as it changes through testing, DoD approved Impact Level 5 GovCloud environment supported production and DISA- supported production. The Contractor shall recommend best practices and follow DoD directives that meet or exceed the PMO objectives for commercial and military standards to provide services to integrate, maintain, and operate delivered capabilities.

The Contractor shall develop a systems engineering management process that provides mutual support for the system specific System Engineering Plan (SEP) (CDRL A005) based on DoD, DLA, Test site, DISA, and DoD approved Impact Level 5 GovCloud environment guidelines.

• System Engineering Plan (SEP) (CDRL A005)

Task 1.6 Configuration Control Governance

The Contractor shall assist the PMO in preparing for and conducting routine and special topic Government Configuration Control governance meetings. The Contractor shall attend Governance meetings, In Progress Reviews (IPRs), meetings with integration/interface representatives of external and internal systems, and special working group sessions, as requested by the PMO.

• White Papers and/or Presentations (CDRL A006)

Task 1.7 Configuration Management (CM)

The Contractor shall develop and deliver to the PMO a CM Plan (CDRL A007) within 30 days after task order award and update annually thereafter. The Contractor shall manage and document the PIEE COE software configuration baseline. The CM Plan shall address the process for any initial solution capability delivery changes, changes to the software, business process, documentation, or any other control item for the established baseline. It should address configuration management administration, configuration identification, configuration control, configuration status accounting, and configuration audit procedures for software and documentation. The Contractor shall modify the CM Plan as required.

The CM Plan shall also include the change or upgrade approval process, as well as the CM audit process. The Contractor shall utilize the PMO’s Serena Dimension or other government approved CM tool to accomplish configuration management tasks and provide deliverables to the Government and to track each trouble ticket and design or software modification enhancement in support of PIEE.

As instructed by the PMO, the Contractor shall provide technical input to modifications on the existing CM Plan.

The Contractor shall assist the Systems Administrators (SAs) at a government approved test site and support the Government CM environment. The Contractor shall provide ongoing technical support for the Government approved CM Tool to include:

• Implementing CM procedures

• Populating of CM database and tool suite

• Maintaining functional, allocated and product baselines

• Testing of newer versions of the configuration management tool suite

• Implementing/migrating CM data to new/additional CM tool sets

• Providing CM data and reports for Management Staff training

• Inputting to Software Configuration Management Plan (SCMP)

• Configuration for components of the CM tool (i.e. Agile, Kanban)

• Preparing baseline and code build for release and application updates

• Ensuring release packages are created and change request are related

• Work with PMO support staff to ensure CM tool folder structure is accurate

• Closing release items 30 days after release implementation in production

• Configuration Management Plan (CDRL A007)

Task 1.8 Weekly Status Report

The Contractor shall prepare a Weekly Status Report (CDRL A008). The intended audience includes Government Program Managers, Product Owners, and the Scrum Team (including external stakeholders). Weekly status reports are due by 3:00 PM Eastern Time on Friday. The weekly status report will include:

• Description of work accomplished (Accomplishments)

• Work planned for the following week (Planned Activities)

• High-level milestone schedule (releases by system) – six (6) month window

• Burndown chart, velocity tracking, and user story backlog (by system)

• Deviations from planned activities (changes in scope)

• Open issues and risks (including remediation plan)

• Weekly Status Report (CDRL A008)

Task 1.9 Monthly Performance and Progress Report (MPPR)

The Contractor shall monitor activities and deliverables under this award and provide a MPPR (CDRL A009) that describes both overall program and individual project progress, issues, problems and their status. The period covered by the MPPR shall include any risks, issues, actions or other MPPR reported information not satisfied or closed in previous reporting periods; and any required interfaces, meetings or other commitments.

The MPPR are due the 5th day of the month or the next following business day. Please note that the Monthly Status Report/Briefing is not required during the Transition-In Activity. The intended audience includes senior management and executive leadership within DoD. The Contractor shall include historical information for trending purposes, and include the following elements:

• Production defect tracking (via escalation to Tier 3 and application performance monitoring), including root cause analysis categorization (e.g. expired certificate, infrastructure outage, source code defect).

• List of Deliverables that were made with due date and the date delivered.

• Requirements Traceability Matrix (RTM): An output of the issue and project tracking tool with information on the story number, the functional grouping, description, rank and priority, associated test case, wireframe/use case level of complexity, level of effort (using Fibonacci series or T-shirt sizes), and the source requestor.

• Risk Register

• Trend Reports o Cumulative Flow Diagram by system o Epic Burndown by system o Release Burndown by system o Version Report by system

• Performance Metric data (monthly) by system:

o Service Desk Incident Count by Tier o Service Desk Incident Summary Report o Peak number of concurrent users for the month o Total authorized user population as of the end of the month o Total users accessing systems during the month (by system or web service)

• Operational Availability (Ao) – Ao = Uptime / (Uptime + Downtime) for each system, sub system, and web service.

• Monthly Performance and Progress Report (MPPR) (CDRL A009)

Task 1.10 Standard Operating Procedures (SOPs)

The Contractor shall develop and implement SOPs (CDRL A010). Each SOP shall be written to be an effective guide for on-boarding resources, scrum and software development activities, workplace logistics, escalation procedures, account and access request processes, and…