DRAFT PWS_DPCAP PDS and V and V Support_01122026.pdf

DOW PROCUREMENT DATA STRATEGY AND VERIFICATION/VALIDATION SUPPORT

DRAFT PERFORMANCE WORK STATEMENT (PWS)

JANUARY 12, 2026

1. Contracting Officer Representatives (CORs).

a. Primary COR.

Name: TBD At Award Organization: OUSD(A&S)/DPCAP Department of Defense Activity Address Code (DODAAC):

HQ0102

Address: 3060 Defense Pentagon, Washington, DC 20301-3060 Phone Number: TBD At Award E-Mail Address: TBD At Award

b. Alternate COR.

Name: TBD at Award Organization: OUSD(A&S)/DPCAP

DODAAC: HQ0102

Address: 3060 Defense Pentagon, Washington, DC 20301-3060 Phone Number: TBD At Award E-Mail Address: TBD At Award

2. Task Order Title. DoW Procurement Data Strategy and Verification/Validation Support

3. Introduction:

It is essential that the Department of War be able to identify, trace, and audit the completeness and accuracy of its procurement data. This requirement supports the Defense Pricing and Contracting (DPCAP) office as it carries out activities central to supporting this effort. It is the expectation of DPCAP that the contractor is an integral member of this team, working with DPCAP, Military Services and Agencies, other office of the Secretary of War, and federal counterparts in implementation of procurement and cross-functional data efforts.

3.1. Mission:

DPCAP is responsible for the functional DoD system/capability requirements, business processes, data standards and associated policy supporting the procurement function across the Department and associated interaction with other Federal Agencies. These requirements/processes/policies are implemented through enterprise systems/capabilities and data standards, Enterprise Resource Planning (ERP) systems and their interfaces, and existing legacy systems and their interfaces. DPCAP coordinates with the Military Components, the Office of Management and Budget (OMB), the General Services Administration (GSA), other federal agencies, and other Office of the Secretary of War (OSW) organizations to accomplish these efforts. The Department has committed to a Procure-to-Pay (P2P) strategy to standardize data and mitigate manual processes to provide traceability and transparency of business actions. DPCAP leads the efforts and initiatives for the DoW procurement community in support of this strategy.

3.2. Background.

Work in this area has been on-going for several years. This is a follow-on effort to a previous task order.

3.3. Objective:

The objective of this effort is to provide DPCAP strategic, operational, and technical support to define required capabilities, data standards, and business processes (including business re-engineering opportunities), conduct research into new and emerging capabilities, support capability pilots (including associated security requirements related to Department of Defense Instruction (DoDI) 8510.01, dated July 19, 2022, subject: Risk Management Framework (RMF) for DoD Systems ), develop associated business cases, maintain DoW scorecards on DoW enterprise procurement related programs (including federal programs implemented in DoW), support implementation efforts with the Components (in their ERP and legacy systems) and at the federal level, and accomplish necessary coordination efforts with Components, other OSW offices, other federal agencies, OMB, etc.

3.4. Scope:

The Contractor shall provide all personnel, equipment, tools, supervision, and non-personal services necessary to support the requirements of the PWS. The Contractor shall designate a Program Manager to provide direction to the Contractor’s employees and serve as a single point-of-contact for the Government’s Contracting Officer’s Representative (COR). Part 3.4.1 of this PWS provides each specific task to be performed.

TASKS

3.4.1. Procurement-related Processes, Requirements, Data Standards and Validation

This task covers several different, yet interrelated areas, in support of the DPCAP-led DoW Procurement Data Strategy. This task requires representing and supporting DoW’s functional and data requirements at the federal level with the Integrated Award Environment (IAE) initiative (managed by the General Services Administration (GSA)) and implementation of the Federal Financial Accountability and Transparency Act (FFATA) and Digital Accountability and Transparency Act (DATA); representing DPCAP with the suite of DoW enterprise procurement-related applications/tools and supporting DoW-wide functional and data requirements; and supporting additional initiatives (including the DPCAP-led set of procurement data standards) related to DoD’s Procurement Data Strategy. Provide technical and functional support to identify DoW enterprise functional and data requirements, standards (including the Procurement Data Standard), business rules and internal controls, processes, and reengineering necessary to achieve business visibility, improve accuracy, and streamline the overall procurement process for the government workforce and industry in accordance with the DPCAP strategic plan. Work with the Components to mature these requirements and implement them in appropriate enterprise systems and processes, as well as in Component procurement and procurement-related applications (including enterprise resource planning (ERP) systems). Maintain the strategic plan document, ensuring appendices and referenced documents are updated as changes occur; support the 5-year renewal cycle of the plan itself.

A. Provide support for DPCAP’s role and functional and data requirements for systems and initiatives within the portfolio of enterprise procurement solutions, enterprise OSD-led efforts, and the IAE portfolio. The contractor shall organize, attend, and facilitate functional requirements meetings in support of DPCAP objectives. Draft implementation and policy-related instructions and memos and assist in coordination with affected stakeholders. Currently, systems and initiatives include, but are not limited to:

o Procurement Integrated Enterprise Environment (PIEE) (and its below modules)

Wide Area Work Flow (WAWF) Electronic Data Access (EDA)

FEDMALL

Procurement Action Required Reporting Online Tools (PARROT, Protest

Tracker, and REA) Surveillance and Performance Monitoring (SPM) Contracting Communication Module (CCM) Contract Deficiency Reports (CDR) Government Furnished Property (GFP) Joint Appointment Module (JAM) Purpose Code Management (PCM) Supplier Performance Risk System (SPRS) Clause Logic Service (CLS) Solicitation Module My Invoice Management Reporting System DoW Hierarchy and Group Access Manager (GAM) Structure o Standard Procurement System (SPS) and Enterprise Contract Writing Module (ECWM) o DoW Procurement Business Intelligence Service (PBIS) in Advana o Commercial and Government Entity (CAGE) Code o Integrated Award Environment (IAE) Portfolio which includes:

SAM.gov (New modernized environment – target environment for all modules) Electronic Subcontracting Plan Reporting (previously eSRS) Subaward Reporting (previously FSRS) Federal Procurement Data System (FPDS) Contractor Performance Assessment Reports System (CPARS) Responsibility/Qualification reporting (previously FAPIIS)

B. Work with the Comptroller, other appropriate OSD offices, and Components through governance groups to ensure appropriate conditions for the procurement data standards and required enterprise systems are placed on Enterprise Resource Planning (ERP) and other target systems.

C. Work with the Components to deploy IAE capabilities and systems (including upgrades);

ensuring implementation supports the Department’s procurement processes and data standards.

D. Draft updates to and maintain the annual Validation and Verification plan for DoW’s procurement data within FPDS and other enterprise systems and support its continued implementation, including collecting and analysis of required Component quarterly reporting.

Additionally, provide support and tracking to DoW’s efforts to comply with FFATA and DATA Acts, and other high visibility initiatives’ reporting requirements.

E. Provide support necessary to the Business Enterprise Architecture (BEA) process which includes inputs for the different BEA products. Work with the Comptroller and other appropriate OSW offices to ensure DPCAP-led data standards and initiatives are incorporated in the recurring releases of the BEA.

F. Provide specific implementation support for the System for Award Management (SAM), SAM.gov, JAM and SPM modules, and miscellaneous small DPCAP pilot efforts as necessary.

Support includes working directly with vendors and DoW personnel to assist them in registering and using the system capabilities.

G. Provide specific compliance tracking for procurement data standard implementation and procure-to-pay exchanges. Work closely with the Components to track progress; maintain status reports and manage the monthly in process reviews.

H. Develop content for training aids for DPCAP-led initiatives, including items to be posted to the

DoD Procurement Toolbox and updates to Warfighting Acquisition University (DAU.edu) courseware.

I. Document procedures for user and office management in FPDS and SAM.gov. Assist the government in ensuring agencies can report to FPDS (including contracts, other transactions, and financial assistance). Identify PBIS/Advana report requirements to support routine requests.

Assist the government in producing the bi-monthly report to USASpending from FPDS.

J. Government Furnished Property (GFP) / Contractor Acquired Property (CAP) process improvement. Review and analyze data flows related to GFP/CAP, and the systems and data standards associated therewith. Recommend improvements to systems, standards, and policy.

Support training in GFP/CAP processes. Participate in GFP Module meetings to identify data requirements and mapping changes. Provide requirements reviews and testing support to improvements in PIEE related to GFP/CAP, including the transition of tools managed by DCMA.

Coordinate closely with OSD Comptroller and OUSD A&S Sustainment for cross-functional issues supporting GFP/CAP including efforts to improve compliance under the Financial Improvement and Audit Remediation (FIAR) program.

K. Intergovernmental Transactions (IGTs) process improvement. Review and analyze data flows related to IGTs, and the systems (e.g., G-Invoicing) and data standards associated therewith.

Recommend improvements to systems, standards, and policy. Support DoW workforce training in IGT processes. Coordinate closely with OSD Comptroller, the Department of Treasury, and the Office of Management and Budget to ensure necessary data standards and processes are included to ensure IGTs that result in assisted acquisitions are compliant with FAR and DFARS processes and DoW PDS.

L. Procure-to-Pay Process Improvement. Assess activities for improved integration of data across acquisition, logistics and finance. Provide subject matter expertise in architecture, technical alternatives, business process re-engineering and functional process improvements. Support training in procurement process improvements. Participate in meetings to identify and implement Procurement Process Improvements.

M. Intelligence Automation Requirements & Prototypes. Work with DPCAP/CeB to identify candidates for prototyping 2-3 intelligence automation efforts (i.e., robotics, artificial intelligence (AI)) to support implementation of procurement data standards and DoW-wide common procurement processes. Develop initial requirements of approved efforts and the prototypes to review the solutions. Identify what additional tasks would be necessary to fully deploy the solutions.

N. Conduct program and project management in association with the overall effort. It includes developing and maintaining business cases and implementation scorecards; communication, training, and outreach; and general meeting support.

O. Develop and maintain Department implementation scorecards for the procurement data standard and purchase request data standard, Contract Reporting to FPDS, and other enterprise initiatives to provide consistent assessments and management of Department data and implementation

P. Work closely with OSD offices and Components to coordinate and communicate all efforts herein. Develop and maintain training and outreach content and materials related to the systems and initiatives listed herein. Attend conferences and workshops to provide training and workshop instruction. Maintain content of the DPCAP/CeB Electronic Business section of DPCAP’s homepage, DoD Procurement Toolbox, and any associated Warfighting Acquisition University (DAU.edu) training modules.

Q. Provide general meeting support, to include scheduling, agendas, minutes, and audio/visual capabilities for DPCAP/CeB led efforts.

R. Provide and manage a transition plan covering both transitioning in and transitioning out tasks.

Provide weekly updates to the government during transition timeframes.

3.4.2. Optional Task – Emerging Initiative Support (Surge)

This task provides surge support and requires supporting DoW’s functional and data requirements at the federal or Department level for requirements and policy support related to managing procurement-related initiatives generated from statute, policy, or updates to the DoD Strategic Plan for Defense-Wide Procurement Capabilities. It may also involve working with the Comptroller and other appropriate OSD offices to develop Business Enterprise Architecture (BEA) products to include business process re-engineering changes emerging from initiatives. This task requires procurement-related subject matter expertise (including areas such as clause logic and property traceability), application/business intelligence development expertise, and/or BEA product development expertise; and will often require requirements research, data analysis, and coordination with component, OSD, and/or federal teams. The task may also result in technical surges to develop new capabilities or priority changes to existing capabilities. Should this surge support result in additional work that is not provided for under Section 3.4.1, the Government and contractor will negotiate an adjustment in price.

Deliverables: Work products in support of tasks

DELIVERABLES AND SCHEDULE

3.4.3 The Contractor shall provide deliverables as specified in the contract to the COR. Final work product/deliverables are considered Government property. If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last workday prior to the due date. All deliverables shall be submitted using Microsoft Office suite of tools (e.g., MS Word, MS Excel, MS PowerPoint), or Adobe PDF format, unless otherwise specified by the COR. Electronic submission shall be made via email, unless otherwise agreed to by the COR. All days identified below are intended to be calendar days unless otherwise specified.

All written documents produced by the Contractor in performance of this contract shall be written in clear, concise, and well-organized language to effectively communicate with the attended audience. The Contractor’s writings shall be written in plain language and comply with DoD Instruction 5025.15, “DoD Plain Language Program.”

Successful performance under this contract requires the creation of quality products, as well as responsiveness of Contractor personnel in the day-to-day interaction with the client and output of work products. Accordingly, the Contractor is required to proactively maintain assigned tasks and be responsive to all entities with professional business dealings related to the assigned tasks.

PWS

TASKS

DELIVERABLE

DESCRIPTION

DELIVERY

TIME

FREQUENCY QUANTITY RECIPIENTS

3.4.1 Strategic Plan

document updates

According to schedule

Bi-annually Ongoing updates, provided 2 times (total per year of contract performance)

COR

3.4.1 Organize, attend, facilitate functional requirements meetings, Draft and socialize agendas;

consolidate and develop briefings;

provide pre-brief materials; develop action matrices and follow up on actions; draft minutes and meeting summary

According to schedule

Weekly and Monthly

Reoccurring/ standing functional meetings normally include 4-5 weekly and 2-3 monthly; as needed

COR

3.4.1 (A-C) (F)(Q)

Functional and Technical Work Products in Support of tasks

According to schedule

Minimum of weekly

As needed COR

3.4.1 (D)

Validation & Verification Quarterly Reporting and Annual Plan

Draft of Annual plan by November 15th;

quarterly V&V summations by end of month following quarterly due dates

Quarterly and annually

Ongoing updates, 4 reports and 1 plan. (Five total between reports and plan)

COR

3.4.1 (E)

BEA recurring updates

According to schedule

Bi-annually Ongoing updates, provided 2 times annually, or more frequently as requested

COR

3.4.1 (G)

Compliance monitoring for PDS

According to schedule

Minimum of Monthly

Ongoing updates, COR implementation and P2P exchange updates provided 12 – 24 times annually, or more frequently as requested

3.4.1 (H)(L) (N)(P)

Develop DPCAP Training Aids, Training and Outreach

According to schedule

Minimum of Monthly

As directed, between 12 – 24, or more frequently as requested

COR

3.4.1 (I)

Report to USASpending from FPDS and Data Analysis

1st and 15th of each month

Minimum of Bi-monthly

Ongoing updates, provided 6 – 12 times, or more frequently as requested

COR

3.4.1 (J)

GFP/CAP Monthly and Bi-annual Reports, and Plan

Annual Plan and bi-annual according to schedule, 1st day of each month for reports

Monthly and bi-annually

Ongoing updates, 12 monthly and 2 bi-annual, and 1 Plan

COR

3.4.1 (K)

IGT Data Standards and Analysis & Reporting

According to schedule

Monthly As needed COR

3.4.1 (M)

Intelligence Automation Requirements & Prototype report

According to schedule

Weekly 52 updates on newly identified automation & sustainment of existing technology

COR

3.4.1 (O)

Quarterly Scorecards on DoW enterprise systems

15th of the month following the end of each quarter

Quarterly and annually

Ongoing updates, 4 reports and 1 annual summary. Five in total (four quarterly reports and one annual summary)

COR

3.4.1 (P)

Maintain DPCAP/CeB Web Content Updates

According to schedule

Monthly Ongoing updates, updates 12 times, or more frequently as requested

3.4.1 (R)

Transition Plan 2 days after award.

As directed Minimal weekly updates until completion of transition

Note: The absence of any contract requirement from this deliverables list shall not detract from its enforceability nor limit the rights or remedies of the Government under any other provision of the contract. The COR has the right to reject or require correction of any deficiencies found in the deliverables. Unless otherwise specified, the Government will have a maximum of ten calendar days from the day the draft deliverable is received to review the document, provide comments back to the Contractor, or approve the deliverable(s). In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection within ten calendar days of receipt.

This is a FAR 16.202-2 firm-fixed-price (FFP) contract. A FFP contract “places upon the contractor maximum risk and full responsibility for all costs and resulting profit or loss. It provides maximum incentive for the contractor to control costs and perform effectively.” FAR 16.201-1. The Contractor is cautioned that the tasks listed in paragraphs 3.4.1. and 3.4.2. of this PWS do not contain quantities or estimated quantities. As such, the FFP effort shall include as much of each PWS task as is needed by DPCAP during the period of performance. Should timely completion of the tasks require more manpower than is contained in the contractor’s proposal, the contractor shall provide extra manpower at its own expense to complete the tasks.

GENERAL REQUIREMENTS

4. General Requirements

This section describes the general requirements for this effort. The following sub-sections provide details of various considerations on this effort.

4.1 Non-Personal Services

The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the Procuring Contracting Officer (PCO) immediately.

4.2 Business Relations

The contractor shall successfully integrate and coordinate all activity needed to execute the requirement.

The contractor shall manage the timeliness, completeness, and quality of problem identification. The contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of any subcontractors. The contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all contractor personnel. The contractor shall ensure cooperation with other contractor support to the DPCAP/CeB office.

4.3 Contract Administration and Management

4.3.1 Contract Management

The contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. The contractor must maintain continuity between the support operations at DPCAP/CEB, 5611 Columbia Pike, Falls Church, VA and the contractor's corporate offices.

4.3.2 Contract Administration

The contractor shall establish processes and assign appropriate resources to effectively administer the requirement. The contractor shall respond to Government requests for contractual actions in a timely fashion. The contractor shall have a single point of contact between the Government and Contractor personnel assigned to support contracts or task orders.

4.3.3 Personnel Administration

The contractor shall provide the following management and support as required. The contractor shall maintain the currency of their employees by providing initial and refresher training as required to meet the PWS requirements. This may include required training from the Warfighting Acquisition University (DAU.edu). The contractor shall make necessary travel arrangements for employees. The contractor shall provide necessary infrastructure to support contract tasks for all off-site support and for individual employees who are normally on-site when conditions require, they work off-site for any period of time.

The Government requires that during a period of administrative closings, including but not limited to weather closings, that the contractor be able to telework. Contract requirements will not ordinarily be abated because of administrative closings.

4.4 Subcontract Management

The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The prime contractor will manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations. Contractors may add subcontractors to their team after notification to the Procuring Contracting Officer (PCO) or Contracting Officer Representative (COR). Cross teaming may or may not be permitted.

STAFFING

4.5 Contractor Personnel, Disciplines, and Specialties

The contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combination of education, training, and experience. Key personnel assigned to this contract must have sufficient experience to perform the work outline in this PWS. One example of highly desired experience is working with the OSD. Desired experience is Joint Staff or Military Department Headquarters. The contractor shall match personnel skills to the work or task. The Contractor shall provide the necessary resources and infrastructure to manage, perform, and administer the contract.

Overall, the complexity of the support required by this contract have historically required a majority of hours performed by senior level personnel.

The Program Manager and any SMEs are designated as Key Personnel. The contractor shall identify key personnel, by name to address the requirements of this PWS. Program Manager is required to be on-site regularly. Additional personnel may be identified for specific areas of the PWS requirements.

However, while a Program Manager is required, the Government does not necessarily require that SMEs be a part of the labor mix on this contract. Any SMEs that are a part of this labor mix are key personnel and subject to the requirements of the following paragraph.

During the first 180 calendar days of performance, the Contractor shall make no substitutions of key personnel unless illness, death, or termination of employment necessitates the substitution. The Contractor shall notify the Contracting Officer as soon as possible after the occurrence of any of these events and provide the information required below. After the initial 180 calendar day period, the Contractor may propose substitutions. The Contractor shall provide a detailed explanation of the circumstances necessitating the proposed substitutions, complete resumes for the proposed substitutes, and any additional information requested by the Contracting Officer. The Contractor shall, prior to making any substitution permanent, demonstrate to the satisfaction of the Contracting Officer that the qualifications of the proposed substitute personnel are at least equal to the requirements identified in the PWS and have the same or greater qualifications as the personnel originally proposed for the position.

The Contracting Officer will notify the Contractor within 15 calendar days after receipt of all required information of the decision on proposed substitutions.

4.5.1 Estimated Labor Mix

Based on historical data, it will take approximately 14,700 hours per contract period (not including optional surge CLINs) and various labor categories to complete the required tasks. The government estimates approximately 7-9 full-time equivalents (FTEs) to effectively perform and meet the objectives of this PWS in its entirety. The Government’s estimate of a labor mix that can perform the required tasks is as follows:

Program Manager

Consultant II

Consultant III

Senior Consultant II

Senior Consultant III

Senior Manager

Functional Specialist SME II

Functional Specialist SME I

Note: the positions listed above are only intended to detail the Government’s estimated labor mix, and do not represent contract requirements.

4.6 Location and Hours of Work

Accomplishment of the results contained in this PWS requires work at DPCAP/CeB, 5611 Columbia Pike, Falls Church, VA (also known as the Suffolk building) and at various contractor, subcontractor, and Government facilities (mainly in the continental United States). Normal workdays are Monday through

Friday except US Federal Holidays. All contractor personnel are expected to be available during 0800- 1700.

Support to the requirements under this PWS may be performed on-site at the DPCAP/CeB (Suffolk building), off-site, or through a hybrid model. Personnel may need to attend meetings at the DPCAP/CeB or other Washington, DC metro area locations. In case of weather or security closures of the DPCAP/CeB office during normal business days, all contractor personnel are expected to work at off-site locations. Daily parking is not generally available for contractors at the Suffolk building; street parking (some metered) is normally available within a 5-10 minute walk.

4.7 Travel

Travel to government facilities or other contractor facilities in the Washington, DC metro area to support the requirements of PWS is often required.

Travel outside the Washington, DC metro area to attend meetings at other government or contractor facilities or to support training events or conferences is minimal (for estimating purposes – 6 3-day trips a year for one person). Most of the contractor team members will also be expected to support the DoW Procure-to-Pay & Financial Audit Training Symposium or similar event to assist the government with presenting certain training sessions. The conference normally is held in Orlando, FL and is three full days with travel occurring on the days before and after the event. Travel cost must be in accordance with FAR 31.205-46. Approval for travel and receipts must be submitted to the KO or COR.International travel is not expected.

The expected travel outlined above shall be considered as a Time and Material line item for the base period and each following option year.

SPECIAL REQUIREMENTS

5. Special Requirements

This section describes the special requirements for this effort. The following sub-sections provide details of various considerations on this effort.

5.1 Security and Safety

Access to classified material is not required for this effort at this time; nor are the DPCAP/CeB facilities classified. Should access to classified information be required in the future, a DD Form 254 will be added to the task order. All contractor personnel with access to unclassified information systems, including e-mail, shall have at a minimum, a favorable National Agency Check (NAC). The on-site employees are required to have a Common Access Card (CAC) assigned and access to A&S email, among other applications; as well as be assigned a building badge that grants access. Most additional personnel may be required during performance to have CACs assigned in order to access government systems. As such, each individual directly supporting the contract must have a favorable NAC completed and recorded in JPAS prior to billing under the contract.

Contractor staff without CACs or building badges that visit the DPCAP/CeB facilities at the Suffolk building during performance of PWS tasks are required to provide government-issued identification (e.g., driver’s license) at the security desk at entrance to the building and be escorted to the DPCAP/CeB office.

Personnel should anticipate a 10-15 minute timeframe under normal conditions. Similar procedures are normally required at all other government facilities as well.

5.2 Transition

The contractor shall follow the transition plan submitted as part of the proposal and keep the Government fully informed of status throughout the transition period. Throughout the phase-in/phase-out periods, it is essential that attention be given to minimize interruptions or delays to work in progress that would impact the mission. The contractor must plan for the transfer of work control, delineating the method for processing and assigning tasks during the phase-in/phase-out periods.

5.3 Government Workspace

The Government will make available office space and communications capability in the DPAC/CeB offices at the Suffolk building for use by the approved contractor personnel in the performance of this contract.

5.4 Environmental Requirements

There are no special environmental requirements in support of this PWS.

5.5 Applicable Directives

There are no additional applicable directives in support of this PWS that are not already incorporated in the ordering contract’s clauses.

QUALITY

6. Quality

This section describes the Quality Control components for this effort. The following sub-sections provide details of various considerations on this effort.

6.1 Quality Control

The Contractor shall develop a Task Order Quality Control Plan (QCP) and maintain an effective quality control program to ensure services are performed in accordance with the IDIQ contract and this PWS. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Contractors QCP is the means by which the contractor assures that work complies with the requirement of the contract.

The finalized QCP will be accepted by the Government at the time of the award of the Task Order. The Contracting Officer may notify the Contractor of required modifications to the plan during the period of performance. The Contractor then shall coordinate suggested modifications and obtain acceptance of the plan by the Contracting Officer. Any modifications to the program during the period of performance shall be provided to the Contracting Officer for review no later than 10 working days prior to effective date of the change. The QCP shall be subject to the Governments review and approval. The Government may find the QCP "unacceptable" whenever the Contractors procedures do not accomplish quality control objective(s). The Contractor shall revise the QCP within 10 working days from receipt of notice that QCP is found "unacceptable."

6.2 Performance Standards.

The Government will assure services meet the requirements of the PWS and will conduct surveillance of Service Provider’s performance through review of deliverables using the performance thresholds below.

Function Measurement Method

Evaluation Metric

Expected Level of Performance (Performance

Objective)

Minimum Acceptable

Performance

Technical content, accuracy, and timeliness

Evaluation by end user.

COR assessment based on review by end user.

Work products contain required and accurate information and are delivered on time at least 95% of the time.

Revisions that occur are minor and are resolved in a satisfactory manner.

90% of the products or tasks meet the acceptable level.

Product or task quality

Evaluation by end user.

COR assessment based on review by end user.

Quality meets or exceeds the specified parameters of the product or task deliverable in more than 95% of the products or tasks.

90% of the products or tasks meet the acceptable level.

Communication and coordination professionalism

Feedback from stakeholders.

COR assessment based on feedback from stakeholders.

No significant complaints received regarding professionalism of contractor personnel.

99% of interactions meet the acceptable level.

SPECIAL CONSIDERATIONS

7. Special Considerations

Identification of Potential Conflicts of Interest (COI) and Non-disclosure Requirements.

The contractor may have access to information under this order that could represent a potential conflict of interest. The government requires non-disclosure agreements to be signed by each of its employees and others performing duties under this order. Agreements are designed to preclude any competitive advantage that may be gained by company use of such knowledge.

Quality Assurance Surveillance Plan The Contracting Officer Representative (COR) as designated in the contract will ensure the required performance standards or service levels are achieved by the contractor in accordance with the latest Quality Assurance Surveillance Plan. The Quality Assurance Surveillance Plan is for Government use only and does not form a part of this contract.