A25a HQ003421R0047AMENDMENT U0001.pdf

HQ003421R0047

FCR1120201431

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

1. To provide a respond to questions received by offerors eletronically via email before the December 30th, 2020 deadline.

2. Changes and corrections made to the solicitation.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 35

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 07-Jan-2021

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HQ003421R0047

X 9B. DATED (SEE ITEM 11)

21-Dec-2020

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

06-Jan-2021

CODE

WHS - ACQUISITION DIRECTORATE

4800 MARK CENTER DRIVE, SUITE 09F09

ALEXANDRIA VA 22350-0002

HQ0034 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

QUESTIONS AND ANSWERS

RFP HQ003421R0047 Questions and Answers

1. Section 4.4.1 states, “Prospective contractors shall provide as part of each’s technical approach proposal package a detailed project work plan.” However, neither the proposal instructions nor the evaluation criteria include a project work plan as part of the technical approach. Please clarify where the project work plan is to be included as part of the technical approach.

Answer: The Project Work Plan is to be included as part of the Technical Approach. PWS at 4.4.1.

2. Are offerors required to complete and return the pricing schedule on pp. 20-21 of the RFP as well as Attachment 1 Price Proposal Breakdown Sheet? If the pricing schedule is also required, should it be included in Volume V Price?

Answer: The Offeror is to complete the pricing schedule on page 23 and page 24 of the RFP.

The Offeror is to complete Attachment 1 Price Proposal Breakdown Sheet and include it in Volume V.

3. FAR provisions 52.204-24 and 52.204-26 are required to be completed and returned with the

Offeror’s proposal. In which volume of the proposal should they be included? Also, please confirm that these pages will not count toward the page limit for the volume.

Answer: FAR provisions 52.204.24 and 52.204-26 will be included as part of the Offeror cover/transmittal letter and it will not count towards the page limits.

4. In which volume of the proposal should the reps and certs with fill-ins (e.g., FAR provision

52.204-8 ANNUAL REPRESENTATIONS AND CERTIFICATIONS (MAR 2020)) be included? Also, please confirm that these pages will not count toward the page limit for the volume.

Answer: FAR provision 52.204-8 Annual Representations and Certifications will be included as part of the Offeror cover/transmittal letter and it will not count towards the page limits.

5. Why are two versions of FAR 52.204-8 (i.e., 52.204-8 ANNUAL REPRESENTATIONS

AND CERTIFICATIONS (MAR 2020) as well as 52.204-8 ANNUAL REPRESENTATIONS AND CERTIFICATIONS – ALTERNATE I (JAN 2020)) included in the RFP? Which one should be completed?

Answer: 52.204-8 Annual Representations and Certifications – Alternate I will be removed from the solicitation. Please review HQ003421R0047 Amendment U0001 in beta.Sam.gov.

6. Is a font smaller than 12 point permitted in headers and footers?

Answer: No, please review HQ003421R0047 Amendment U0001 in beta.Sam.gov.

7. The page limitation for Volume IV Past Performance excludes “Past Performance

Questionnaires submitted by Government officials.” However, no questionnaire was provided with the RFP. Are questionnaires required? If they are, when will they be available to offerors?

Answer: Questionnaires are not required, please review HQ003421R0047 Amendment U0001 in beta.Sam.gov.

8. Attachment 2 Key Personnel Chart uses both 10-point and 11-point font. Please confirm that this is an acceptable exception to the requirement for minimum 12-point size font.

Answer: 52.212-1 Instructions to Offerors (3) has been revised to include the following:

Text must be easily readable (e.g. single or double spaced, with minimum one-inch margins, able to be printed on 8½ x11 inch paper, minimum of 12-point size font);

however; the font size for Attachment 2 Key Personnel Chart will be 11-point size font.

Please review HQ003421R0047 Amendment U0001 in beta.Sam.gov.

9. In Attachment 2 Key Personnel Chart, please confirm that “Copies of certificates shall be made available” means “available upon request from the Government.”

Answer: Attachment 2 Key Personnel Chart revised; please review HQ003421R0047 Amendment U0001 in beta.Sam.gov.

10. Request the solicitation closing date be extended 7 days.

Answer: The RFP will not be extended at this time.

11. Please confirm that we need to submit Past Performance Questionnaire(PPQ) for this effort and should be from our customers

Answer: All related language related to Past Performance Questionnaires have been removed.

Please review HQ003421R0047 Amendment U0001 in beta.Sam.gov.

12. Please provide PPQ related instructions to Offeror

Answer: The PPQ requirement is no longer applicable; please review HQ003421R0047 Amendment U0001 in beta.Sam.gov for revised instructions.

13. Whom should we submit the PPQ Point of Contact(POC)

Answer: The PPQ is no longer applicable; please review HQ003421R0047 Amendment U0001 in beta.Sam.gov.

14. Please share the PPQ Template for Past Performance reference submission

Answer: The PPQ is no longer required; please review HQ003421R0047 Amendment U0001 in beta.Sam.gov.

15. Can we show subcontractor past performance to cover Eval Criteria - Factor 3(a)

Answer: Yes

16. Do commercial experience count for this effort?

Answer: Yes; please refer to 52.212-2, Section 2.2 Factor 3(a) and Section 2.3.

17. Have these services been performed in the past; or is this a new requirement?

Answer: The services are currently being performed under Contract No. HQ003417P0110.

18. Is there an incumbent contractor currently performing these services?

Answer: Yes; the services are currently being performed under Contract No. HQ003417P0110.

19. Is this a follow-on requirement; if so please provide the previous contract or task order number?

Answer: No; this is not a follow-on requirement. Please refer to the answer from question 17.

20. Can a small business (with no facility clearance) team with a large business who has a top secret facility clearance team together to meet the requirement?

Answer: No; the small business prime Offeror is required to have the necessary facility clearance.

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

CONTINUATION/TRANSITION

OF THE

COMPTROLLER EXTENSIBLE MARKUP

LANGUAGE (XML) EXHIBITS TOOL

FOR

DEFENSE TECHNICAL INFORMATION CENTER (DTIC)

1. INTRODUCTION

The Comptroller XML Exhibits (CXE) tool requires the continuation of support to continue planned application improvements, prepare for and support the FY 2023 Budget Estimate Submission through the FY 2027 President’s Budget request budget cycles. The contractor will provide expert application and Financial Management Regulation (FMR) user support, provide indexing and ingestion support of data generated by the Budget Estimate Submission and the President’s Budget request for both analytics tools (Kibana and Qlik) and keep the application and documentation prepared for the transition to another DoD Agency’s supported environment.

2. BACKGROUND

The Comptroller XML Exhibits was first implemented during the FY 2009 Budget Estimate Submission cycle for Research, Development, Test, and Evaluation (RDT&E) Budget Exhibits. The CXE application expanded to include all RDT&E Budget and Procurement exhibits in 2012. The application has been used in 38 separate Program Objective Memorandum (POM), Budget Estimate Submission, President’s Budget request and Amended budget submission cycles and is an essential component within the Department of Defense's (DoD) Budget Formulation process. It integrates 350 RDT&E and 150 Procurement budget exhibits created by all DoD components into 75 standard, well formatted, validated, and math checked Justification Books, suitable for submission to Congress. Mandated by policy, the Budget Estimate Submission is required to be submitted to the Office of the Under Secretary of Defense, Comptroller (OUSD(C) each September and mandated by law, the President’s Budget request must be delivered to Congress every year during the first week of February.

Prior to CXE, the primary tools for creating Budget Exhibits for Congress were Microsoft Word and Microsoft Excel. The process created a high degree of inconsistent and inaccurate exhibits across the DoD. The implementation of the CXE application created consistent math and format checked exhibits for all DoD Services (Army, Navy, Marine Corps, and Air Force) and Agencies.

DTIC, through its contractor support, has developed and implemented the complete set of RDT&E and Procurement exhibits, including the Shipbuilding and Conversion, Navy (SCN) Procurement budget exhibits, and supported multiple Office of the Secretary of

Defense Federal Financial Management Regulation (OSD / FMR) reform efforts.

Completely redesigned the RDT&E User Interface (UI) to take advantage of the latest web technologies, incorporating an updated modern user interface to parallel the layout of the actual published exhibits so that entering data is more intuitive for users. Deployed the CXE application on the SIPR classified network, giving the Intelligence Community the ability to submit XML based classified budgets and used for the first time during the Budget Estimate Submission for FY 2017. Completed development of a set of analytics tools and populated them with all the Budget Estimate Submission and President’s Budget request data generated by the CXE tool since the 2009 President’s Budget request. Developed and implemented significant application and administration enhancements and user requested changes, including the Program Resources Collection Process (PRCP) Validation Tool. Completed an automated workflow process that moves finished exhibits to OUSD(C) Analysts and the Office of Management and Budget (OMB) Examiners for final review prior to submission to Congress. Supported multiple unplanned budget submission requirements including separate Overseas Contingency Operations (OCO) and amended and supplemental budget submissions, which have occurred during administration changes.

2.1 Services are performed in four (4) categories:

2.1.1 Business process re-engineering

2.1.1.1 This includes efforts focused on implementing application fixes and enhancements based on user input and OSD guidance, including development of appropriate business rules that govern the data, insuring that all exhibits and Justification Books prepared are suitable for submission to Congress.

2.1.1.2 All implementations within the application are be compatible across the utilizing DoD Components’ formulation processes and tool sets.

2.1.2 Information Technology (IT) development

2.1.2.1 Information Technology development is focused on advanced

XML applications development with the caveat that all solutions provided and leveraged with DoD Components must be open source.

2.1.2.2 Even as the DoD Components become more advanced in their use of XML, the interface interoperability of their budget formulation tools with the CXE tool remains an ongoing challenge requiring collaboration between the CXE software engineers and the DoD Components.

2.1.3 Budget Estimate Submission and President’s Budget request budget submission support

2.1.3.1 The over 400 registered DoD users, from the all DoD Services and Agencies, who use the CXE application to prepare their budgets require a considerable amount of customer support. This support consistently begins at least six (6) weeks prior to submission deadlines and often requires support during off-duty times weekdays and weekends. Service/Agency users change regularly and new users of the application require the most support.

2.1.3.2 Bugs encountered with the application during budget submissions require immediate attention from the team’s developers.

2.1.3.3 The team reacts frequently to application changes requested by OUSD(C) while budget submissions are underway.

2.1.4 Analytics

2.1.4.1 The contractor facilitates the ingestion of the annual Budget

Estimate Submission and the President’s Budget request cycle data into the Kibana and Qlik Sense applications.

2.1.4.2 The current process involves ingesting and testing initial annual budget data indexes in DTIC’s local version of Kibana (a component of the Elastic Stack) then copying the data into the OUSD(C) Advana Qlik Sense analytics tool for OUSD(C) management and analyst use for analyzing year over year budget data.

3. SCOPE

This effort reflects a continuation of existing work already in support of the Comptroller's XML Exhibit tool. DTIC seeks non-personal services for the Comptroller’s XML Exhibit tool. The Contractor shall maintain and monitor current functionality of the Comptroller's XML Exhibit tool and the design and development of necessary enhancements.

3.1 Customers

The OUSD(C) customer user community for this PWS includes all DoD users who access the DTIC CXE systems, totaling in excess of 400 individuals in OSD, the military departments, and the defense agencies. However, the Contractor will respond directly to the DTIC PM and Contracting Officer Representative (COR) to satisfy requirements in support of all users.

3.2 Services Provided

This PWS will provide all of the IT services and support for DTIC and OUSD(C) mission systems required for submission of RDT&E and Procurement budget exhibits by OUSD(C) customers and CXE application users and must support the classification level of Secret.

These services are defined as Mission Essential Support Services, which include but are not limited to the following:

Program Management and Transition Activities

Subject Matter Expert Business Analysis for all related to the Financial Management Regulation (FMR) and related business rules

Mission Operational Support Software Engineering and other Support Services Mission Application and Database Support Information Assurance/Cyber Security Quality Assurance

3.3 Current Contract Support

Current contract support is provided by the Washington Headquarters Services Acquisition Directorate (WHS/AD) in their Alexandria, VA location. The contract number is HQ003417P0110. The contract is on its last Option Year and it will expire on March 29, 2021. The current Level of Effort (LOE) is approximately seven (7) contractor Full-Time Equivalents (FTEs) with approximately 1,945 hours per year per FTE.

4. PERFORMANCE REQUIREMENTS

Contractor shall have a thorough understanding of OUSD(C) and DTIC’s organization and Enterprise infrastructure. Anticipated labor categories and requirements across all functional areas are specified in Section 10 of this PWS. Contractor shall use Government Furnished Equipment (GFE) and Government-approved procedures to provide services required.

Contractor shall use Government-furnished support systems, including trouble ticket systems, network management systems, and personnel to carry out all tasks required.

Contractor’s technical approach will be clearly identified as part of the proposal and shall demonstrate the following:

Well-defined support organization and support procedures Strong software engineering expertise Well-designed and documented technical architectures using DoD architecture framework solutions and mission applications Strong knowledge of Information Assurance requirements for mission application development Value-added innovative thinking is encouraged. Whenever possible, Contractor shall recommend changes that improve service, improve IT security, enhance customer capability, and/or reduce cost.

4.1 The Contractor shall complete planned application modernization improvements.

4.1.1 The Contractor shall continue the implementation of CXE User Interface modernization requirements, which include converting application parts built with Apache Tapestry to AngularJS including:

Site Landing page

Entire RDT&E user interface Entire Procurement user interface Justification and Master Justification Book Wizards Application Administration Sections Business Rules Administration Sections

4.1.2 Improvements: The Contractor shall implement performance improvements to the CXE application.

4.1.2.1 Contractor shall move from the current Apache Cayenne database framework to Hibernate.

4.1.3 Contractor shall provide Financial Management Regulation (FMR) revision support and align the CXE application with FMR changes.

4.1.3.1 Contractor shall modify existing exhibits and develop new, sample exhibits that illustrate the future model.

4.1.3.2 Contractor shall update the schema, code base, business rules, user interface, and Web Services.

4.1.3.3 Contractor shall prepare briefings for joint OUSD(C) and DoD

Component working groups that describe the current model and alternative future models.

4.1.3.4 Contractor shall prepare and submit to the OSD Comptroller a change page for the Financial Management Regulation (FMR) when changes are required. The change page will denote any recommended changes to FMR wording such as updates to budget exhibits, funding thresholds, etc. All changes must be ready for publication, detailing the exhibit format, data definitions, and business rules that must be followed based on the FMR, for incorporation into the application via an external web service.

4.1.4 Contractor shall provide updates to the automation of business rules documentation and incorporate into site downloads section of the user interface.

4.1.5 Contractor shall perform CXE application code platform lifecycle updates and upgrades.

4.2 The Contractor shall prepare for and support the 2023 Budget Estimate

Submission through the 2027 President's Budget request submission cycles.

4.2.1 Contractor shall perform Business Process Reengineering (BPR) methodologies to capture functional requirements.

4.2.2 Contractor shall define business rules within the XML validation code that ensures budget exhibits' data and formats adhere to the DoD FMR.

4.2.3 Contractor shall refine existing RDT&E and Procurement budget exhibits schemas, Extensible Stylesheet Language Transformations (XSLTs), XML Schema Definition (XSDs), business rules and code base to accommodate lessons learned and requirements generated from each successive budget submission.

4.2.4 Contractor shall document resulting functional requirements in a format and to a level of completeness suitable for development.

4.2.5 Contractor shall document resulting business rules in a format suitable for the Comptroller Community as well as developers.

4.2.6 Contractor shall participate in Agile development methodology, including development of product backlogs, participation in sprints, reviews, and other meetings as requested by the Government Program Manager (PM).

4.2.7 Contractor shall develop and maintain the XSDs and XSLTs, Database

Design Model, Domain Object Model, User Interface, and Web Services in the UNIX operating system and MySQL database hosted at DTIC.

4.2.8 Contractor shall develop test plans, perform unit and integration testing in local and development environments and full regression testing in staging and production environments.

4.2.9 Contractor personnel performing software services and Security Reviewer roles shall maintain DoD IT Level 1 certification.

4.2.10 Contractor shall perform routine maintenance, defect repair, updates to code resulting from lifecycle upgrades to the platforms that support the software application.

4.2.11 Contractor shall perform administrative record keeping, journals, transaction logs, and updating of architecture documentation IAW the DoD Chief Information Officer DoD Architecture Framework (DoDAF) requirements.

4.2.12 Contractor shall provide similar support for the maintenance and modification of all previously implemented years RDT&E and Procurement exhibits.

4.3 Annual integration of Budget Estimate Submission and President’s Budget request analytics datasets into the analytics and visualization tools.

4.3.1 Contractor shall annually integrate new data into the current data analytics and visualization suite for CXE analytics.

4.3.1.1 Contractor shall design and create ad hoc or customized reports using current data analytics and visualization tools, as needed.

4.3.1.2 Contractor shall develop a Secret Internet protocol Router (SIPR) network version of the current analytics and visualization tools.

4.3.2 Contractor shall populate the existing analytics dataset annually, starting with President’s Budget request 2022 for RDT&E and Procurement budget exhibits, including Navy SCN data

4.3.3 Contractor shall recommend and implement resolutions to the differences between the data provided in XML across these cycles.

4.3.4 Contractor shall provide ad hoc query support to the OUSD(C), DoD Services and all DoD Agencies as required.

4.3.5 Contractor shall provide data mapping services to other DoD Services and DoD Agencies when requested (Budget Estimate Submission mapping requires need to know).

4.3.6 Contractor shall analyze customers' needs and create ad hoc and customized reports, as needed.

4.3.7 Contractor shall prepare data from pre-XML reports to make it available for expanded trending analytics.

4.4 Transition for Contract Start (Incoming Successor Contractor)

4.4.1 Prospective contractors shall provide as part of each’s technical approach proposal package a detailed project work plan. The plan shall include the contractor’s understanding of the business processes of Comptroller XML Exhibits (CXE) tool for post- award activities and what steps will be put in place to mitigate risk to the government.

4.4.2 Successor contractor shall submit all Visitor Authorization Requests (VARs) and Non- Disclosure Agreements (NDAs) to the COR for processing as soon as the contract is awarded.

4.4.3 All key contractor personnel shall be available and committed to start on the first day of the contract Period of Performance (PoP) and have a Secret or Interim Secret clearance. The Contractor shall provide a signed letter of commitment by key personnel within 15 days of PoP. Interim Secret clearances are valid for one year, at which point a Secret clearance is required before contractors can perform work relative to this PWS.

4.4.4 All key contractor personnel must be in-processed on the first day of the contract PoP, through DTIC Human Resource/Security Office and complete the mandatory Information Security Briefing before any computer system access can be granted.

4.5 Transition to Successor (End of Contract)

The contractor shall, no later than 30 days before the completion of the contract, submit a detailed transition plan, and timetable for implementing the transition to the Government for the transfer of all materials and data stored by the contractor to the successor contractor. The timetable for transition shall be no less than one week but no longer than three weeks. This plan shall include a quality assurance element that provides for determination that all files and data have been completely and accurately transferred to the successor contractor.

The incumbent contractor shall provide all reasonable support to the succeeding contractor to ensure orderly transition and minimize any impact to the Government. Unless otherwise specified by the Government, the incumbent contractor shall provide the successor contractor all records (paper, and electronic copies, exercise materials, databases, reports, instructional courseware, etc.) of completed and ongoing projects. This will also include all archived and backup materials. In addition, as an On the Job Training (OJT) function throughout the Transition Phase, the incumbent shall allow the succeeding Contractor to observe (over-the- shoulder) the performance of all PWS required efforts on a not-to-interfere with the on-going support basis. The contractor shall provide the successor contractor with detailed briefings regarding the policies and procedures for managing all aspects of the project. As part of these detailed briefings, the contractor shall provide the successor contractor with all documentation related to the PWS.

The incumbent contractor will cease operations and vacate all government facilities by 2400 hours (midnight) on the last day of the existing contract, unless mutually agreeable arrangements have been made in advance with the COR or the Contracting Officer (KO). Any problems encountered in the transition of services with the predecessor or successor contractor will be immediately reported to the COR. The KO, acting on information provided by the COR, has the sole authority to handle any interference issues.

4.6 Contractor shall prepare financial and administrative reports.

4.6.1 Contractor shall prepare monthly hours worked report for each Full Time

Employee and for each Contract Line Item Number

4.6.2 Contractor shall prepare a weekly activity report for software development activities in progress and completed

5.0 SECURITY

5.1 Contract employees will not access Independent Research and Development

(IR&D) data. Contract personnel will notify the COR if accessing IR&D data is necessary in the course of performing requirements under the contract.

5.2 Facility Clearance (FCL) & Personnel Clearance (PCL). The Contractor shall possess and maintain a SECRET facility clearance from the Defense Counterintelligence and Security Agency (DCSA). The Contractor’s employees, performing work in support of this contract shall have been granted a SECRET security clearance from the DoD Central Adjudication Facility (DoD CAF).

5.3 Physical Security. The contractor will be issued a Common Access Card (CAC) and facility accesses, in the performance of this contract.

5.4 Identification of Contractor Personnel. The contractor(s) must identify themselves as a DoD/DTIC Contractor when identifying themselves to other DoD/DTIC personnel.

5.5 Security Restrictions. During the performance of this contract, the contractor will not move, remove, or relocate any equipment or equipment components without obtaining approval from the DTIC Security Manager.

5.6 All security classification guidance will be provided on a DD Form 254, Department of Defense Contract Security Classification Specification (hereafter referred to as the DD 254). Any changes or additional security classification guidance shall be provided to the contractor in writing, through updates and contract modifications to the DD 254. At no time will the contractor accept classification guidance in any other form. A DD 254 applies, and will be coordinated between the COR and the contractor. A final copy shall be sent to the Contracting Officer to incorporate into the contract.

5.7 ACCESSIBILITY REQUIREMENTS

Any and all electronic and information technology (EIT) developed, procured, maintained or used through this effort, including but not limited to websites, shall meet the applicable accessibility standards at 36 Code of Federal Regulations (CFR) 1194. 36 CFR 1194, which implements Section 508 of the Rehabilitation Act of 1973, as amended, and is viewable at http://www.section508.gov.

6.0 PERFORMANCE REQUIREMENTS SUMMARY

Performance Objective Reference Paragraphs

Surveillance Method

Frequency Performance Threshold

Complete planned application modernization improvements

4.1 and subcategories 4.1.1, 4.1.2, 4.1.3, 4.1.4, and 4.1.5

TPOC Review Monthly Contractor is required to perform with 95% accuracy

Prepare for and support the 2023 Budget Estimate Submission through 2027 President’s Budget request submission cycles

4.2 and subcategories 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.2.5, 4.2.6, 4.2.7, 4.2.8, 4.2.9, 4.2.10, 4.2.11, 4.2.12

TPOC Review Monthly Contractor is required to perform with 95% accuracy

Conduct annual integration of Budget Estimate Submission and President’s Budget request analytics datasets into the analytics and visualization tools.

4.3 and subcategories 4.3.1, 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7

TPOC Review Annually Contractor is required to perform with 95% accuracy

Transition for Contract Start (Incoming Successor Contractor)

4.4 and subcategories 4.4.1, 4.4.2, 4.4.3, and 4.4.4

COR/TPOC

Review

Beginning of Contract

Contractor is required to perform within 95% accuracy

Transition to Successor (End of Contract)

4.5 COR/TPOC

Review

30 Days prior to end of

Contractor is required to perform with 95% accuracy

7.0 Hours of Operations

The Contractor shall provide support services Monday through Friday, between operating hours of 0700 to 1800. The Contractor shall conduct business as necessary to meet the requirements of this order. There may be occasions when contractor personnel will be required to work beyond normal hours of operation in order to accommodate DTIC and support of a task. Contractor shall support weekends and evenings, as required, in order to accommodate user support during each budget cycle (the Budget Estimate Submission and the President’s budget request). All work to be performed outside of the normal operating hours will be approved by the COR prior to commencing the work. Adjustments to Contractor work schedules will not be considered overtime.

7.1 TELEWORK

The Government may permit telecommuting (telework) by contractor employees when determined to be in the best interest of the Government in meeting work requirements (e.g. COOP) and only if the contractor has a SECRET facility clearance. The contractor must have an established program subject to review by the Government. All telecommuting agreements must be authorized and approved by the Contracting Officer Representative (COR) and include date, time, and description of the work to be performed

Telework will be at no additional cost to the Government. Upon approval, the Government may provide as Government Furnished Equipment (GFE): Secure laptop with access to the required portals, networks, and business applications.

Internet connection will not be furnished, therefore, Internet access shall be provided by the contractor

7.2 TRAVEL

The Contractor is not required or authorized to travel in support of this requirement.

contract year

Prepare financial and administrative reports

4.6 and subcategory

4.65.1 and 4.5.2

COR/TPOC

Review

Monthly/ Weekly

Contractor is required to perform with 95% accuracy

Prepare administrative reports 4.6 and subcategory 4.6.2

COR/TPOC

Review

Weekly Contractor is required to perform with 95% accuracy

8.0 QUALITY ASSURANCE

8.1 The Contractor is responsible for implementing and maintaining a Quality Control

Plan (QCP) that identifies and results in the correction of potential and actual problems. The Government shall rely upon the Contractor to implement a Contractor designed QCP that ensures that service will be performed in accordance with this contract, commercial standards, and applicable laws. The QCP shall be implemented on the first day of contract performance. The QCP shall encompass all positions the Contractor is supplying to the Government during the Period of Performance.

8.2 Notwithstanding the Contractor’s QCP, the Government will establish a Quality

Assurance Surveillance Program (QASP) to ensure that the services rendered by the Contractor are acceptable and meets the Government’s minimum requirements. The Government’s QASP will address what deliverables are recommended for surveillance and the method and surveillance periodicity to ensure the quality of deliverables as outlined in this PWS. The QASP addresses what will be reviewed and shall outline actions to be taken by the Government, should review(s) and inspections identify areas requiring remedial action. Of special interest to the Government are performance standards or metrics that address productivity, and completion times.

8.3 Periodic Progress meetings: The Contractor shall participate in periodic progress meetings. The COR will apprise the Contractor of how the Government views the Contractor’s performance and the Contractor shall apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government and may be in the form of telephone or video-conferencing and on-site meetings mutually agreed by both parties.

9.0 INCIDENTAL GOVERNMENT FURNISHED ITEMS & SERVICES

9.1 Facilities and Equipment: The Government will provide on-site workspace and office equipment (e.g., desk, chair, computer, printer, copier, telephone, and consumer operating supplies) to contractor staff to provide the support outlined in the PWS. The Contractor shall be responsible for keeping the provided workspace areas in a clean and orderly condition.

9.2 Information: The Government will provide information, materials, and forms unique to the Government for supporting the task. The COR will be the point of contact for identification of any required information to be supplied by the Government. The information may include: Standard Operating Procedures, DoD Manual 5200.01 “DoD Information Security Program: Protection of Classified Information”, DoD Manual 5200.2-R “Personnel Security Program”, and DoD 5220.22-M, “National Industrial Security Program Operating Manual”

(NISPOM).

9.3 Tracking: The Government will maintain a current listing of contractor personnel assigned laptops and smart phones.

9.4 Other: Personal or company use of phones, utilities, computers, printers, or copiers not directly related to the required services under this contract is strictly prohibited. Contractor shall not remove any government-furnished equipment or supplies from the worksite without approval from the COR. The Contractor shall only use government-furnished facilities, equipment, and supplies to accomplish the tasks required under this contract. The Government will not reimburse the Contractor for any supplies.

10.0 CONTRACTOR QUALIFICATIONS

10.1 Smoking/Alcohol Policy: The Contractor shall comply with local command smoking policies and comply with all applicable Federal statutes, laws, and regulations for alcohol use in the workplace. Copies of policies will be provided to the Contractor by the local command at performance start date.

10.2 Drug Policy: The Contractor shall comply with all applicable Federal statutes, laws, and regulations to implement a Drug Free Workplace Program (DFWP).

10.3 The Contractor shall maintain appropriate dress standards for an office setting.

10.4 The Contractor shall provide courteous and professional service.

10.5 Contractor shall provide sufficient numbers of personnel with appropriate skills and security clearances to effectively and efficiently perform required tasks and meet performance and quality standards.

10.5.1 Contractor shall provide one (1) Program Manager who is also equivalent to a Senior Software Engineer with a minimum of five (5) years of experience at a senior level, also experienced with managing a software development team.

10.5.2 Contractor shall provide one (1) Business Analysts/Subject Matter Expert

(SME) who has at least five (5) years of experience in the following areas:

10.5.2.1 Providing technical writing support for documentation, systems requirements and training material for all components of the software including the User Interface

(UI).

10.5.2.2 Analysis of business requirements derived from the DoD Financial Management Regulation (FMR) and client needs that will be vetted by the Comptroller.

10.5.2.3 Interpretation of analysis that defines the structure of related budget data for creation/modification of the associated XML schema and UI.

10.5.2.4 Design of prototype templates used in both generating PDF documents from XML data combined with XSL and XSLT, and UI development.

10.5.2.5 Composing and documenting business rules to be enforced by the software schema and UI, updated regularly based on system changes and new requirements.

10.5.2.6 Assisting in all aspects of XML/UI testing, including, but not limited to, accuracy of mathematical computations, data validation and business rules enforcement, XML to PDF conversion, and the generation of budget Justification Books.

10.5.3 Contractor shall provide a minimum of three (3) mid-level and one (1) senior-level Software Engineers to perform the required software development in this PWS. The mid-level software engineers must have a minimum of two (2) years of experience and the senior-level software engineer must have a minimum of five (5) years working with the following software development tools:

Java 8 Core Spring Boot 2 SOAP Web Services REST/Jackson Web Services MySQL 8 Hibernate 5 Maven 3 Jenkins 2 Jira 8 Apache Cayenne 7 Apache Tapestry 4 JQuery 3 AngularJS and Angular 8

10.5.4 Contractor shall provide one (1) Software Quality Assurance (QA) Tester with at least two (2) years of QA experience testing Java applications and experience performing the following duties:

10.5.4.1 Develop and maintain software test procedures for

performing testing of existing and newly developed systems, system modifications and software defect repair

10.5.4.2 Develop and maintain software manual test cases and

automated test scripts for performing independent testing of system/software change requests

10.5.4.3 Conduct functional tests on both the web application and web service to verify that the system change requirements are satisfied and standards are implemented.

10.5.4.4 Execute load tests and tune application performance

10.5.4.5 Establish and maintain a software documentation library for all systems’ documentation, to include system specifications, user documentation, standards, and procedures

10.5.5 Contractor shall complete the Key Personnel Chart in the solicitation for each Key Personnel listed in the PWS.

11.0 KEY PERSONNEL

Senior-Level Program Manager/Software Engineer (PM) Position requires DoD Secret Security Clearance Estimated to be Staffed by - 1 FTE

Senior-Level Business Analyst/Subject Matter Expert Position requires DoD Secret Security Clearance

Software Quality Assurance (QA) Tester Position requires DoD Secret Clearance

12.0 CONTRACTOR PERSONNEL

12.1 Compliance with Law. In accordance with Public Law 105-270, Section 5 (2) (A), Contractors shall not perform inherently governmental functions. Section 5 (2)(A) of this Public Law defines the term “inherently governmental function” as “a function that is so intimately related to the public interest as to require performance by Federal Government employees.

12.2 Contractor personnel performing services shall be required to comply with

Government and installation rules and regulations applicable to conduct, safety, security, and procedures governing site entry and exit.

12.3 When performing the tasks associated with this PWS, Contractor personnel shall clearly identify themselves as a Contractor and have a readily distinguishable identification badge and not DoD employees.

12.4 Contractor personnel cannot manage, supervise, or task DoD civilian employees or military personnel while performing services under their contract.

12.5 Contractor personnel shall not establish an employee-employer relationship with DTIC. Contractor personnel shall not provide personal services to DTIC under this contract.

12.6 Contractor personnel cannot make any commitment of U.S. Government funds or resources unless specifically authorized.

12.7 Normal government business workday consists of the hours between 0730-1600, Monday through Friday, except for federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

12.8 NON-DISCLOSURE AGREEMENT (NDA)

The Contractor may be required to access Confidential, Proprietary and/or Sensitive Information held by the Government related to the tasks to be performed under this contract. In consideration of the Government granting the Contractor access to this information, a NDA shall be required between the Contractor and the Government. This form shall be signed by all contract personnel working under this contract and submitted upon contract award. If contractors are replaced during the performance of this contract, then new contract employees shall sign the NDA Form upon beginning work.

12.9 TRAINING

The Contractor shall participate in organizational training as required.

The Contractor shall complete the OSD mandatory training on an annual basis, which may include Operations Security (OPSEC) Training, OSD Counterintelligence Awareness & Reporting, OSD/WHS Privacy Act Training, and Cyber Awareness training, and the Contractor shall comply with all WHS and OSD Operational Security guidelines and directives.

12.10 Federal Holidays to include Presidential Executive Orders:

New Year’s Day 1st of January Dr. Martin Luther King’s Birthday 3rd Monday in January President’s Day 3rd Monday in February Memorial Day 5th Monday in May Independence Day 4th of July Labor Day 1st Monday in September Columbus Day 2nd Monday in October Veteran’s Day 11th of November Thanksgiving Day 4th Thursday in November Christmas Day 25th of December

13.0 CONTRACT OVERSIGHT

13.1 The Contractor shall provide a single point of contact for all contract supervision and performance related matters. The Contractor’s Point of Contact shall ensure that all requirements are performed and that deliverables are submitted.

13.2 The Contractor shall schedule a Kick-Off meeting within seven (7) business days of contract award. The kick-off meeting shall include a Project Management Plan (PMP) as described in section 12.3. The kick-off meeting may be accomplished by teleconference or virtual environment based on current local regulations for gathering in a COVID-19 environment. The Government will approve the kick-off meeting format.

13.3 The Contractor shall deliver a PMP that details the technical approach to meet all deliverables. The Contractor shall deliver the final PMP within fifteen (15) business days of the contract award. The plan must incorporate the technical approach chosen to fulfill the requirements and shall be submitted for review and approval by the Government. The PMP plan shall describe, in detail, the Contractor’s technical approach for each aspect of the tasks outlined herein. It shall include discussion of risk management, quality, technical management approach, quality assurance, communications, staffing, and schedule.

14.0 PLACE of PERFORMANCE and Points of Contact (POC)

The work outlined in this PWS will be performed at DTIC offices located at:

8725 John J. Kingman Road, Fort Belvoir, VA 22060

Contracting Officer Representative (COR) Shirley Kye

Telephone: (571) 448-9705 Email: Shirley.y.kye.civ@mail.mil

Technical Point of Contact (TPOC) Bruce Gilbert Telephone: (571) 448-9789 Email: bruce.w.gilbert.civ@mail.mil

Acronyms

CXE Comptroller XML Exhibits DoD Department of Defense FMR DoD Financial Management Regulation FY Fiscal Year IT Information Technology NIPR Non-Secure Internet Protocol Router network OMB Office of Management and Budget OUSD(C) Office of the Under Secretary of Defense Comptroller POM Program Objective Memorandum RDT&E Research, Development, Testing and Evaluation SIPR Secret Internet Protocol Router network UI User Interface XML Extensible Markup Language

XSD XML Schema Definition XSLT Extensible Stylesheet Language Transformations

Definitions CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

CONTRACTING OFFICER (CO). A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government.

Note: The only individual who can legally bind the Government.

CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S.

Government appointed by the CO to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

PERFORMANCE REQUIREMENTS SUMMARY. Includes the tasks, service or requirement being measured, mapping back to the performance work statement, including the specific paragraph in the PWS. a performance indicator or quality standard

PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

QUALITY ASSURANCE. The Government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.

WORK WEEK. Monday through Friday, unless specified otherwise.

52.212-1 INSTRUCTIONS TO OFFERORS--COMMERCIAL ITEMS (JUN 2020)

(a) North American Industry Classification System (NAICS) code and small business size standard. The NAICS code(s) and small business size standard(s) for this acquisition appear elsewhere in the solicitation. However, the small business size standard for a concern which submits an offer in its own name, but which proposes to furnish an item which it did not itself manufacture, is 500 employees.

(b) Submission of offers. Submit signed and dated offers to the office specified in this solicitation at or before the exact time specified in this solicitation. Offers may be submitted on the SF 1449, letterhead stationery, or as otherwise specified in the solicitation. As a minimum, offers must show--

(1) The solicitation number;

(2) The time specified in the solicitation for receipt of offers;

(3) The name, address, and telephone number of the offeror;

Electronic Submission:

Submit any questions electronically via email regarding the Request for Proposal (RFP) to the following point of contact and include the proposal number (HQ003421R0047) no later than 12:00 pm Eastern Time on December 30, 2020. Any questions received after deadline may not be answered.

Frederick Ray, Contract Specialist Email: frederick.c.ray.civ@mail.mil Telephone: 571-289-6643

Submit proposals electronically via email to the following point of contact and include the proposal number, (HQ003421R0047) in the subject line of the email no later than 12:00 pm Eastern Time on January 12, 2021 . Hard copy submissions shall not be considered or evaluated.

Frederick Ray, Contract Specialist Email: frederick.c.ray.civ@mail.mil Telephone: 571-289-6643

The Proposal must be clear, concise, include sufficient detail for an effective evaluation, and must substantiate the validity of stated claims.