A03 DCATS Support Services PWS rewrite WHS format_Rev 527.docx
DOCX document 119 KB Posted
- Attached to
- Managed Service Provider
- Solicitation number
- HQ003424RXXX2
- Issued by
-
DOD Washington Headquarters Service
About this file
This is a Performance Work Statement (PWS) for IT operational support services for the Department of War Office of Inspector General's Defense Case Activity Tracking System, Enterprise (D-CATSe) and related business systems.
The Government requires comprehensive non-personal IT operational support across a portfolio of systems built primarily on Microsoft technologies, including Azure, M365, Dynamics CRM, SharePoint, and SQL Server. The contract type is Firm-Fixed-Price Level-of-Effort (FFP-LOE) with a base period of one year and four one-year option periods. The primary place of performance is Mark Center, 4800 Mark Center Drive, Alexandria, VA 22350, with telework authorized as determined by the Contracting Officer's Representative (COR). Contractor personnel must maintain Secret facility clearance and interim Secret security clearance, complete mandatory annual cybersecurity training, and obtain Common Access Cards (CACs) for facility access. Service hours are 7:00 a.m. to 7:00 p.m., Monday through Friday, excluding federal holidays.
The scope encompasses 11 primary subtasks under Task 1 (D-CATSe): Program Management, Project Management, Risk Management, Requirements Management, Systems Engineering, System Design, Configuration/Change Management, Test and Evaluation, Operations/Maintenance/Sustainment, Help Desk, and Continuity of Operations Planning. D-CATSe must maintain 99% uptime across 24/7/365 operations supporting 900 current users expected to double by 2027. Task 2 covers DefenseReady system support with optional elements including software development and data analytics. All deliverables must be 90% accurate/error-free with any required revisions resolved within one week and accepted by the KO/COR. Key personnel include a Program Manager (BA/BS in technical or managerial discipline with 10+ years experience) and Senior Systems Engineer with expertise in software systems development and network engineering. The Government furnishes workspace, computers, and information services; the Contractor furnishes all other supplies, equipment, facilities, and services. Surge support over the contract life shall not exceed 25% of total proposed cost/price.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ADAP TEMPLATE 211-002 PERFORMANCE WORK STATEMENT (PWS) JUL 2025
Defense Case Activity Tracking System, Enterprise (D-CATSe) Support Services for the Department of War Office of Inspector General
PART 1
GENERAL INFORMATION
1. INTRODUCTION: This is a non-personal services contract to provide IT operational support. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn, is responsible to the Government.
2. BACKGROUND: The DoW OIG identifies, deters, and investigates fraud, waste, and abuse in the DoW. The DoW OIG keeps the Secretary of Defense and Congress fully and currently informed of fraud, waste, abuse, and deficiencies. The DoW OIG reports to the Secretary of War, the Congress, and recommends corrective actions in cases of fraud, waste, abuse, and deficiency; and on the progress made in implementation of corrective actions. The DoW OIG serves as the primary proponent for the Defense Inspector General (IG) system, for all Military Service, Component, and other IGs assigned to DoW. The DoW OIG has Special Agents, Investigative Personnel, Auditors, and Evaluators who must operate globally, conducting criminal and administrative investigations, audits, and evaluations to support the mission of the DoW OIG - ultimately supporting the DoW and the Warfighter.
DoW OIG organizational interfaces include Mission Support Team (MST) and Defense Criminal Investigative Service (DCIS) Senior Staff, the Defense Business System (DBS) Program Management Offices (PMO), the Office of the Chief Information Officer (OCIO), the MST Acquisition Directorate (AQD), and other front-end DoW OIG business Components.
· MST Senior Staff
· To be apprised of ongoing contractual activities, as well as engaged on strategic and collaborative organizational initiatives.
· DBS PMOs
· Manage cost, schedule, performance, and risk of their respective systems.
· Lead the management, oversight, and implementation of application development and operational support.
· Include project and technical management integration points, intent on collaborating with Contractor personnel to maintain the highest level of quality and productivity for operational systems.
· OCIO
· Include project and technical management integration points, accountable for the following.
· Funding, sustainment, and performance of the DoW OIG DECC infrastructure and platform support, remediation of any associated application availability impediments, and vendor access requests for maintaining DoW OIG applications.
· Funding, sustainment, and performance of all cybersecurity and information assurance functions, maintaining oversight and authority to formally accept risk on behalf of the DoW OIG.
· Sustainment and performance of a central IT license repository, managing and procuring all licensing, reporting regular status updates and notifications of their successful renewals.
· Disaster Recovery, Continuity of Operations (COOP), and back up and restoration of DoW OIG applications and services in accordance with the COOP Manager.
· AQD
· Contractual conduit positioned between the PMOs and Washington Headquarters Services/Acquisition Directorate, designating a Contracting Officer’s Representative (COR); assisting with contract consultation, review, and modifications.
· DoW OIG front-end business Components
· Leaders of DoW OIG business operation, customers of each PMO, operating as independent Functional Sponsors, providing Subject Matter Expertise (SME) resources regarding their business processes, developmental requirements, and operational needs.
· End state, they are the reason for the support required – executing the DoW OIG’s mission on a daily basis.
3. DESCRIPTION OF SERVICES: The Contractor shall provide IT operational support across a portfolio of like-systems and technologies as defined in this PWS except for those items specified as government furnished property and services. The Contractor shall perform to the standards in this contract.
4. OBJECTIVES:
· To acquire IT operational support across a portfolio of like systems and technologies, intent on realizing improved quality and performance for our customers, as well as gaining cost efficiencies across the task areas specified in Part 5, specific tasks
5. SCOPE: The DoW OIG is seeking support services, to supply holistic IT support. This partner will collaborate with DoW OIG personnel to oversee our portfolio of systems – ensuring quality, performance, and efficiencies are realized. They will provide strategic and tactical support, integrating with all DoW OIG echelons and external entities. The DoW OIG requires DoW-approved industry standards and best practices to implement and sustain mature capabilities. These requirements are necessary to support various Functional Sponsors and customer bases, to include internal and external Federal organizations. Internal to DoW OIG, these entities include Administrative Investigations, the Defense Criminal Investigative Service, and other DoW OIG organic personnel. The designated service provider will be our primary IT operational support integrator for the systems listed, collaborating with DoW OIG and existing Contractor personnel.
The Government may require surge support during the base or any option period, and surge modifications will be within the scope of the contract and provide increased support for the defined task areas of this PWS. Surge support over the life of the contract will not exceed 25% of the contractor’s total proposed cost/price for the base and all option periods, excluding any six-month extension of services pursuant to FAR 52.217-8.
6. PERIOD OF PERFORMANCE: The Period of Performance (PoP) will consist of a base period of 1-year with four 1-year option periods starting as specified in the contract/task order award.
7. CONTRACT TYPE: The Government will award a Firm-Fixed-Price Level-of-Effort (FFP-LOE) contract.
8. PLACE OF PERFORMANCE: The primary place of performance will be at the Mark Center, 4800 Mark Center Drive, Alexandria, VA 22350 and the contractor’s site. The labor categories will be divided as necessary between the Mark Center and the contractor’s site.
9. TELEWORK: As determined by the COR, contractor employees may work at an alternate place of performance (e.g., home, the contractor's facility, or another approved activity within the local travel area) on a regular, reoccurring basis or in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, government closure due to inclement weather, etc.). Additionally, the contractor shall account for the whereabouts of their personnel should this information be requested by the COR. Non-emergency/non-essential contractors should not report to a closed government facility. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. The contractor shall use best efforts to provide the same level of support as stated in the PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer (KO) or the contractor may request an equitable adjustment pursuant to the Changes clause of the contract.
10. HOURS OF OPERATION: The Contractor is responsible for providing services, between the hours of 7:00 a.m. to 7:00 p.m., Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The Contractor must maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.
11. RECOGNIZED HOLIDAYS: Government personnel observe the following holidays as governed by 5 U.S.C. § 6103. Government facilities will be closed and unavailable to Contractor personnel:
| New Year’s Day |
| Labor Day |
| Martin Luther King Jr.’s Birthday |
| Columbus Day |
| Washington’s Birthday |
| Veterans Day |
| Memorial Day |
| Thanksgiving Day |
| Independence Day |
| Juneteenth National Independence Day |
| Christmas Day |
*If the date falls on a Saturday, the Government holiday is the preceding Friday. If the date falls on a Sunday, the Government holiday is the following Monday.
In addition to the days designated as holidays, the Government observes the following days:
· Any other day designated by Federal Statute
· Any other day designated by Executive Order
· Any other day designated by the President’s Proclamation
12. QUALITY CONTROL/ASSURANCE:
12.1. Quality Control: The Contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. For both positive and negative performances, ratings shall be recorded in the Contractor Performance Assessment Reporting System (CPARS).
12.2. Quality Assurance: The Government shall evaluate the Contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s). Performance standards are detailed in Part 5 and summarized in Technical Exhibit 1.
13. PERSONNEL MATTERS
13.1. Key Personnel: The personnel listed below are considered essential to the work being performed hereunder. Prior to substituting, removing, replacing, or diverting any of the specified individuals, the Contractor shall notify the Contracting Officer 15 working days in advance and shall submit a written request and justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on this Contract. The proposed substitution of personnel must meet or exceed the education, experience, and other technical requirements of the personnel being replaced. No change in personnel shall be made by the Contractor without the prior written consent of the Contracting Officer.
13.2. The following personnel are considered key personnel by the government:
Program Manager. Serves as the program manager for any complex or a group of projects affecting the same common/standard/migration system) and shall assist the Operations/Program Manager in working with the Government Contracting Officer Representative (COR), Government management personnel and customer agency representatives. Under the guidance of the Operations/Program Manager, responsible for the overall management of the specific task order(s) and insuring that the technical solutions and schedules in the PWS are implemented in a timely manner. Performs enterprise wide horizontal integration planning and interfaces to other functional systems. Education/Experience: BA/BS in a technical or managerial discipline and with at least 10 years of experience. Leads medium to large complex projects and major phases of large projects. The senior consultant also manages the fact-finding analysis and development of hypothesis/conclusions, production of final reports and delivery of presentations. Responsible for ensuring that the project delivers to client expectations on time and to budget.
Senior Systems Engineer. Highly specialized in one or more phases of software systems development, systems integration, or network engineering. Acts independently under general direction. Provides technical assistance and advice on complex activities. Formulates / defines specifications, develops / modifies / maintains complex systems and subsystems, using vendor engineering releases and utilities for overall operational systems. Applies analytical techniques when gathering information from users, defining work problems, designing technology solutions, and developing procedures to resolve the problems. Develops complete specifications to enable computer programmers to prepare required programs. Analyzes methods of approach. Reviews task proposal requirements, gathers information, analyzes data, prepares project synopses, compares alternatives, prepares specifications, resolves processing problems, coordinates work with programmers and engineers, and orients users to new systems. Works with considerable freedom to make decisions on the techniques and approaches to be used. Prepares recommendations for system improvement for management and user consideration.
13.3. The Contractor shall provide a Project Manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the Contractor when the manager is absent shall be designated in writing to the Contracting Officer. The contract manager or alternate shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. The contract manager or alternate shall be available between 7:00 a.m. to 7:00 p.m., Monday through Friday except Federal holidays or when the government facility is closed for administrative reasons.
13.4. Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed.
13.5. Special Qualifications: N/A.
14. SECURITY:
14.1. Contractor shall have an active Secret Facility Clearance at the start date of contract and shall maintain the level of security required for the life of the contract. All contractor personnel performing work under this contract shall have at minimum an interim Secret Clearance. Contractor personnel who currently hold dual citizenship and/or active foreign passports must report possession of a foreign passport to the OIG Office of Security. U.S. passports are required to be utilized when traveling overseas. Contractor personnel must report any use of a foreign passport to enter or exit the United States to the Contractor Facility Security Officer (FSO). The FSO shall follow guidelines as set forth within the SECURITY EXECUTIVE AGENT DIRECTIVE 4 (SEAD 4)
14.2. Physical Security: The Contractor shall be responsible for safeguarding all Government equipment, information and property provided for Contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured. Contractor personnel shall comply with all local security requirements including entry and exit control for personnel and property at the government facility.
Visit Authorization: The Contractor and/or subcontractor(s) are responsible for submitting a visit authorization letter via the Defense Information System for Security (DISS) to the DoW OIG OSEC after personnel have been approved to perform on the contract. The DoW SMO Code will be provided to the Company Facility Security Officer (FSO) upon request.
14.3. Building Access: The Contractor shall be required to obtain a Common Access Card (CAC) for OIG network usage and DoW physical facilities access. It shall always be worn on the upper part of the body so as to be clearly visible and concealed on your person whenever the wearer leaves the DOW OIG premises for any reason or any length of time. CACs are government property and shall be returned upon departure or at the conclusion of the contract (whichever comes first) to:
Department of War Office of Inspector General ATTN: Industrial Security Program Manager 4800 Mark Center Drive, Suite 09B24 Alexandria, VA 22350-1500 Contractors whose CAC is lost or stolen must present documentation with immediate supervisor’s signature, to OSEC or CAC sponsor identifying that the CAC is missing and describing the circumstances under which the loss occurred. OSEC or CAC sponsor will provide an official memorandum for the badge office in order to receive a new CAC. The CAC contains personally identifiable information and must be treated as a controlled item.
The Contractor's staff must not share their CAC and passwords with any other staff member. The COR will report any violation or suspected violation to the Contracting Officer and OSEC. Any violators will be temporarily or permanently removed from the project. If a Contractor has a CAC issued from a previous engagement with another agency that CAC must be returned to that agency before issuance of a DoD OIG sponsored CAC.
14.5. Mandatory Training. All selected contractor personnel are required to complete the following mandatory annual training courses to comply with the DoW OIG contractor security policy listed below. The annual mandatory training in addition to other policies and procedures for the DoD OIG and Pentagon Annex of War (formally Mark Center) will be provided along with the mandatory security briefing, as well as the executable Classified Information Nondisclosure Agreement, SF 312.:
· Cyber Awareness Challenge Personally Identifiable Information
· Anti-Terrorism Level 1
· DoD Security Awareness,
· Preventing Violence in the Workplace
· Counterintelligence Reporting and Awareness training
· Insider Threat Awareness,
· OPSEC Training,
· Unauthorized Disclosure of Classified Information
· Introduction to Information Security
· Controlled Unclassified Information
15. CONTRACT ADMINISTRATION
15.1. Post Award Conference/Periodic Progress Meetings: The KO, COR, and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings the Contracting Officer will apprise the Contractor of how the Government views the Contractor's performance and the Contractor will apprise the Government of problems, if any, being experienced.
15.2. Phase-in/Phase-out Period:
· Transition-In (Phase In): All key personnel/key positions must be onboard at start of the PoP. Fifty percent of total staffing must be completed within 30 days of the start of the PoP and 100 percent within the following 2 weeks.
· Transition-Out (Phase Out): The Contractor will need to collaborate with the Mission Partner at least 120 days or sooner, prior to the end of the contract, to develop a transition-out plan IAW FAR 52.237-3.
16. TRAVEL/TDY/DEPLOYMENT
Contractor travel will not be required.
17. OTHER DIRECT COST (T&M and LH): There are no other direct costs authorized by this contract.
18. DATA RIGHTS: The Government has unlimited rights to all documents/material produced under this contract.
19. CONFLICT OF INTEREST:
19.1 Organizational Conflict of Interest/Personal Conflict of Interest: Contractor and Subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interest (OCI) as defined in FAR Subpart 9.5 as well as personal conflicts of interest. Using the Contractor OCI/ COI Disclosure Form, the Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential conflict and shall promptly submit the conflict-of-interest disclosure form to the Contracting Officer to avoid or mitigate any such conflict.
19.2 The Contractor’s mitigation plan will be reviewed and accepted/rejected solely at the discretion of the Government, and in the event the Government unilaterally determines that any such conflict cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the conflict.
19.3 In addition, Contractors shall conduct internal reviews as necessary to identify financial interests and determine if any personal conflicts of interest exist or may arise. The Contractor shall ensure that the organization has analyzed each financial disclosure to determine whether actual or potential conflicts exist. Information should be gathered and analyzed for all governing body members (e.g., board of directors, trustees, etc.) and principals of the organization as defined by FAR 52.203-13 and for each manager and key personnel who would be or are involved with the performance of the contract.
19.4 All Contractor and Subcontractor employees supporting this contract shall sign the WHS AD non-disclosure agreements.
PART 2
DEFINITIONS & ACRONYMS
2.1. 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 (KO): A person with authority to enter into, administer, 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 Contracting Officer to assists in administering the contract. 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.
· KEY PERSONNEL: Contractor personnel required to be used in the performance of the contract as indicated in the Key Personnel section listed in the PWS.
· 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.
2.2. ACRONYMS:
| AQL |
| Acceptable Quality Level |
| BPR |
| Business Process Reengineering |
| CAC |
| Common Access Card |
| CCB |
| Configuration Control Board |
| CIO |
| Chief Information Officer |
| CM |
| Configuration Management |
| CONUS |
| Continental United States (excludes Alaska and Hawaii) |
| COOP |
| Continuity of Operations |
| COR |
| Contracting Officer Representative |
| COTS |
| Commercial-Off-the-Shelf |
| CPARS |
| Contractor Performance Assessment Reporting System |
| DD 254 |
| Department of Defense Contract Security Classification Specification (DD Form 254) |
| DFARS |
| Defense Federal Acquisition Regulation Supplement |
| DOW |
| Department of War |
| FAR |
| Federal Acquisition Regulation |
| FTE |
| Full Time Employee |
| HIPAA |
| Health Insurance Portability and Accountability Act of 1996 |
| KO |
| Contracting Officer |
| LCAT |
| Labor Category |
| NCR |
| National Capital Region |
| OCONUS |
| Outside Continental United States (includes Alaska and Hawaii) |
| ODC |
| Other Direct Costs |
| PIPO |
| Phase In/Phase Out |
| POC |
| Point of Contact |
| PRS |
| Performance Requirements Summary |
| PWS |
| Performance Work Statement |
| QA |
| Quality Assurance |
| QAP |
| Quality Assurance Program |
| QASP |
| Quality Assurance Surveillance Plan |
| QC |
| Quality Control |
| QCP |
| Quality Control Program |
| SF 312 |
| Classified Information Non-Disclosure Agreement (SF 312) |
| TDY |
| Temporary Duty Travel |
| TE |
| Technical Exhibit |
| WHS |
| Washington Headquarters Services |
PART 3
GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES
3.1. Facilities: The Government will provide the necessary workspace for the contractor staff to provide the support outlined in the PWS to include desk space, telephones, and other items necessary to maintain an office environment at the Mark Center.
3.2. Equipment: Computers furnished under this contract shall be used for official business only. Contractor personnel shall not install any software on Government furnished computers unless consent is obtained from the KO or COR.
3.3. Information: Government Furnished Property (GFP) will be provided for the performance of the tasks listed. See GFP Attachment. Information services available on the Government furnished computers (e.g., DISANet, Internet, email) shall only be used for official business.
PART 4
CONTRACTOR FURNISHED ITEMS AND SERVICES
4.1. General: The Contractor shall furnish all supplies, equipment, facilities, and services required to perform work under this contract that are not listed under Section 3 of this PWS. The contractor shall prepare all deliverables and other contract documentation utilizing contractor resources.
4.2. Clearance: The Contractor shall possess and maintain a Secret facility clearance from the Defense Counterintelligence and Security Agency at time of proposal as stated in the attached DD 254. The Contractor's employees, performing work in support of this contract shall have been granted an interim Secret security clearance at minimum from the Defense Counterintelligence Security Agency (DCSA) prior to be granted a CAC.
PART 5
SPECIFIC TASKS
5.1 Task 1 – Defense Case Activity Tracking System, Enterprise (D-CATSe).
D-CATSe is the authoritative case management system of the DoW OIG for administrative investigations. The application offers a central point of management for DoW OIG Hotline, Investigations of Senior Officials, and Whistleblower Reprisal Investigations business units, from first contact through case closure. Additionally, other Service and Component IGs across the DoW are or will begin utilizing D-CATSe for their own administrative investigations. The application is built upon multiple Microsoft technologies, incorporating custom code as required. It is hosted in an on premise, DoW OIG operated environment. The system will be scaled to support upwards of 4,000 users worldwide, requiring 24 x 7 operational support, inclusive of the task areas listed within the PWS. D-CATSe requires dedicated management and technical support, ensuring premier application supportability for enterprise-wide DoW utilization.
Additional Details:
· Microsoft technologies, to include but not limited to Azure and related infrastructure/software components, M365 and related infrastructure/software and data components, Dynamics Customer Relationship Management (CRM), SharePoint, SQL, Identity Management, , and Exchange.
· Additional technologies, including but not limited to, phone, voicemail, and fax ingestion related to application ingestion and routing of DoW OIG Hotline contacts.
· System reliability, availability, and maintainability goals are: 24 hours, 7 days per week, 365 days per year, no less than (NLT) 99% up-time, supporting CONUS/OCONUS users.
· User-base/growth: 900 users currently and expected to double that amount in 2027. Infrastructure, platform, and application footprint to be provided as supplemental information.
· Production, staging, and training environments.
5.1.1 Subtask 1.1 – Program Management.
Program Management support is required to plan, prepare for, and collaborate with DoW OIG leadership on holistic management and oversight functions, to include contract modifications, status reports, financial reviews, schedule changes, and risks. In addition to meeting or exceeding industry standard experience and qualifications regarding program management, an advanced understanding of DoW operations is required.
The Contractor shall:
1. Coordinate with COR.
1. Apprise senior management on productivity and quality assurance via informal updates and Senior Staff Briefings.
1. Develop rough order of magnitude (ROM) estimates for contract modifications.
1. Develop and maintain a Program Management Plan, as well as transition and migration plans.
1. Support Government efforts for document review and approval.
1. Gather stakeholder requirements.
1. Manage project schedules and coordinate Contractor activities in accordance with the PWS.
1. Identify and communicate issues/risks to the Government and offer recommendations on how issues/risks should be mitigated to successfully satisfy the requirements.
1. Notify the COR when the Contractor believes any Government activity may impact performance, schedule, or cost.
1. Draft and deliver Monthly Status Reports (MSR), inclusive of weekly status report content and other critical aspects of contract oversight and program health.
Task 5.1.1 Program Management
| Performance Standard |
| Acceptable Quality Level (AQL) |
| Surveillance Method |
| Program Management |
| Performance/Deliverables: |
~ Program Management Plan (due within 15 days of contract award; updates as required) ~ Monthly Status Report (monthly) ~ Rough Order of Magnitude (as required)
Inspection of delivered materials.
| Task Elements: a) – j) |
| Documentation regarding deliverables will require government acceptance |
Error Density: Fewer than 5 minor errors (spelling, grammar, formatting) per 10 pages, and zero major errors (factual inaccuracies) per document
Any required revisions to deliverables:
~ within 1 week
5.1.2 Subtask 1.2 – Project Management
Project Management support is required to effectively manage each DoW OIG system and provide active direction to ensure risks and opportunities are adequately addressed. In addition to meeting or exceeding industry standard experience and qualifications regarding project management, an advanced understanding of DoW operations is required. Project Managers will oversee all operational support activities, collaborating with and providing status updates to corresponding DoW OIG personnel.
The Contractor shall:
1. Develop project plans, charters, schedules, and a cumulative work breakdown structure that align with DoW guidance and PMO requirements.
1. Formulate best practices, strategies and objectives to meet the PMO’s mission, short, mid, and long-term planning goals as well as optimize organizational structure and processes to more effectively achieve the mission for COR review
1. Provide technology recommendations to facilitate the ability to achieve business objectives. Identify and develop business processes and performance measures to successfully integrate systems development, implementation, and sustainment.
1. Identify, review, and assess the impact of emerging DoW/Federal/Commercial policies, directives, guidelines, DoW initiatives, governance processes, and technologies of each system.
1. Establish a governance process to develop and adjudicate the standards, policies, and processes needed to effectively and efficiently manage device configuration policies and applications.
1. Develop ad hoc documentation required by Government representatives.
1. Support activities of the PMOs to include meeting preparation and facilitation, preparing and conducting briefings, and developing options/white papers describing potential technical design and deployment alternatives.
1. Provide project updates to Government counterparts via weekly status reports.
Task 5.1.2 Project Management
| Performance Standard |
| AQL |
| Surveillance Method |
| Project Management |
| Performance/Deliverables: |
~ Project Plans (per project) ~ Project Charters (per project) ~ Project Schedules (per project) ~ work breakdown structure (within 15 days of contract award; updates as required) ~ weekly status reports (weekly) Inspection of delivered materials.
| Task Elements: a) – h) |
| Contain required information, 90% accurate/error free, and delivered on time. |
Any required revisions:
5.1.3 Subtask 1.3 – Risk Management
Risk management support is required to actively manage system risks, issues, and opportunities. In addition to meeting or exceeding industry standard experience and qualifications regarding risk management, an advanced understanding of DoW operations is required. Requested support will lead and/or collaborate on risk management plans, assessments, prioritization, and mitigation activities – maintaining quality and performance expectations per system and associated user-base.
The Contractor shall:
1. Provide a comprehensive risk management plan to address, identify, assess, and provide prioritization of risks (including how risks will be recorded, reported, and mitigated, and communicated), issues, and opportunities. Plan shall include the full range of risks that could impact the project including but not limited to resources, access, physical and cybersecurity, and unplanned events.
1. Identify high risk factors in support of the Risk Management Board targeting the reduction or elimination of risk.
1. Mitigate any schedule or deployment risks/issues, as well as notify Government personnel of opportunities that could result in positive impacts to system sustainability and user-base expectations.
1. Develop and maintain a risk register to address individual risks, prioritize risk actions, and detail a mitigation plan for each risk identified.
1. As part of the MSR, the risk register shall include detailed information on how the Contractor managed previous risks.
Task 5.1.3 Risk Management
| Performance Standard |
| AQL |
| Surveillance Method |
| Risk Management |
| Performance/Deliverables: |
~ Risk register (maintain list of identified risks (review monthly) ~ Risk Management Plan (due 30 days after start) ~ Risk Management Board (monthly) Inspection of delivered materials.
| Task Elements: a) – e) |
| Contain required information, 90% accurate/error free, and delivered on time. |
Any required revisions:
5.1.4 Subtask 1.4 – Requirements Management, Analysis, and Assessment Requirements management support is necessary to plan the transformation and maturation of DoW OIG systems and environments, including detailed analysis of system requirements, drafting of new requirements, establishing traceability between those requirements and customer needs, and confirming delivery of the associated capabilities upon completion. An auditable and centralized means of managing requirements, including active collaboration with respective Government personnel, is required.
The Contractor shall:
1. Perform system requirements analysis and provide functional and engineering requirements. This analysis shall include generation of technical performance measures and the outlining of test and evaluation objectives.
1. Assist in analyzing current support requirements and capabilities in relation to existing functions, operations, technology, and technical trends.
1. Develop requirements baseline and update requirements per guidance, architectural/infrastructural changes, and stakeholder discussions.
1. Develop a repeatable process via requirements management plan to document requirements and ensure traceability to properly generate test cases/use cases.
1. Implement and maintain a requirements traceability matrix (RTM), capturing initial and future requirements baselines.
1. Trace capabilities with requirements and maintain updates within the RTM.
1. Maintain and update the requirements management process to ensure the integrity of approved baseline requirements, while collecting, vetting, and documenting new requirements within the process.
1. Conduct surveys, interviews, and research to develop solution strategies for alternative opportunities. Address the feasibility of developing standards or offer an alternative approach for capabilities that cannot be delivered through a common, industry-based standard.
1. Perform system requirements analysis consisting of a structured approach to translate users’ needs into a technical system, product definitions as well as functional and engineering requirements.
1. Conduct analysis, identify “as-is” and “to-be” processes, collect relevant data, information, and documentation to formulate and implement a solution or recommendation.
1. Develop data collection methods and tools to monitor status and provide updates when changes occur.
Task 5.1.4 Requirements Management, Analysis, and Assessment
| Performance Standard |
| AQL |
| Surveillance Method |
| Requirements Management, Analysis, and Assessment |
| Performance/Deliverables: |
~ Requirements Traceability Matrix (as required) ~ requirements management plan (as required) ~ business cases (as required) Inspection of delivered materials.
| Task Elements: a) – k |
| Contain required information, 90% accurate/error free, and delivered on time. |
Any required revisions:
5.1.5 Subtask 1.5 – Systems Engineering
Systems engineering support is required to manage environment and application specifications, interfacing with all other task areas to ensure the quality, sustainability, and security of all systems. This support will provide guidance and leadership among Contractor operational support, ensuring resilient system architecture is correctly configured and maintained, keeping up to date with modern technologies and providing recommendations for future system upgrades and enhancements. Expertise in the supported solutions and their underlying technologies is required. Within this task area, cybersecurity support is also required and should be performed in accordance with DoW standards, as found in the latest National Institute of Standards and Technology (NIST), DoW Instructions, and Defense Information Systems Agency (DISA) issued guidance. This support must report through the DoW OIG Designated Approving Authority (DAA) – the Chief Information Officer (CIO) or designee(s), for identification, mitigation, and formal acceptance of risk. Application security posture shall be maintained as to eliminate all incidents, to include but not limited to spillage.
The Contractor shall:
1. Create technical specifications from functional specifications for complex development projects.
1. Develop technical documentation, which shall adhere to Information Technology Infrastructure Library (ITIL) standards.
1. Create and interpret representations of systems in all applicable DoW Architecture Framework (DOWAF) views.
1. Develop input, review content, and revise existing documentation on strategic integration, data strategy, architecture, and tactics. Validate integration testing of newly developed application solutions.
1. Be responsible for validating the software solution and each update can be installed successfully in the environment and is responsible for identifying any additional factors that need to be considered for successful deployment.
1. Provide feedback to development and test teams of environmental or security changes that need to be accounted for.
1. Ensures environment resiliency, identifies, and corrects areas of performance degradation. Provides recommendations for performance enhancements.
1. Perform for root cause analysis of reoccurring operational issues, interfacing with other IT support organizations as needed to identify and correct the issue. Complete after-action reports (AARs) and update any necessary systems documentation to reflect the result. A central repository of AARs must be maintained in support of regular reviews.
1. Implement procedures and operate the tools that shall provide confidentiality, integrity, availability, authenticity, secure access control, survivability, and non-repudiation of information on agency software, hardware, and networks.
1. Implement mechanisms to provide the capability to preserve, protect, detect, react, revise, and recover from threats, intrusions, and denial of services. The procedures/mechanisms shall be implemented to adequately protect network, server, mobile devices, workstations, communication security and physical facilities.
1. Support Government requirements to accomplish submitting new and amended Certification and Accreditation (C&A) packages including system configuration of all components.
1. Perform capacity planning no less than quarterly and also prior to each additional component onboarding. Engineers/administrators shall verify that the local load balancing/sharing is adequate or if additional servers or other associated equipment needs to be integrated. If a need for additional capacity is required to support the load increase, a business case shall be forwarded to the Government for review and consideration.
1. Set performance baselines and monitor environment for changes in those standards.
1. Perform review of change/configuration management activities, including but not limited to operations/maintenance activities and deployments into all environments.
1. Participate in design sessions of new system components as the technical subject matter experts of the application, ensuring that additions and modifications to the existing environment are seamlessly integrated with the established environment.
1. Engage with application development personnel; to verify and validate application updates are within compliance of DoW OIG owned/operated environments, and to assist systems administrators in performing any application updates required to continuously maintain quality and performance standards.
1. Draft, deliver, and implement data migration plans for ingesting new customers and data from their legacy systems.
Task 5.1.5 Systems Engineering
| Performance Standard |
| AQL |
| Surveillance Method |
| Systems Engineering |
| Performance/Deliverables: |
~ data migration plans (per external entity onboarding) ~ business cases (as required) Inspection of delivered materials.
| Task Elements: a) – q) |
| Contain required information, 90% accurate/error free, and delivered on time. |
Any required revisions are:
~ Resolved within 1 week ~ Accepted by KO/COR
5.1.6 Subtask 1.6 – System Design
System design support is required to document and maintain system design tasks in coordination with DoW OIG personnel. Highly trained personnel are necessary to assist the Government with gathering requirements, plans, architecture, design, development, testing, and deploying OIG systems. System design personnel will engage with customer teams to design project structures and plans, help gather and analyze technical requirements, develop conceptual architecture and system designs, build models, and assist in the development of effective technical solutions.
The Contractor shall:
1. Identify and analyze design issues; consider design alternatives and present a recommended solution.
1. Integrate the work of the system design, development, testing, and C&A teams to provide an integrated and coherent approach to deployment.
1. Determine the necessary attributes for successful system deployment and develop and coordinate detailed implementation plans for each system deployment or modification.
1. Develop design documents that serve as the basis of all staging, configuration, and testing efforts. Support a design review session to validate the design information. Ensure system stability and provide orientation, knowledge transfer and technical consulting services.
1. Develop comprehensive unclassified architectures to include sub-functional systems and partner network interfaces to include Architecture Views, Diagrams, and Artifacts.
1. Assess capability gaps of the current architecture and develop an architecture roadmap/transition plan based on “as is” architecture and the “to be” architecture. Recommend and define the software and hardware specifications to support the “to be” architecture. Provide technical insertion services to support architecture modifications to integrate solutions into the current baseline.
1. Conduct simulation modeling, data traffic flow analysis, network bandwidth analysis, performance and bottleneck analysis, design trade off analysis, load balancing and scalability analysis to validate architecture development artifacts.
1. Maintain and update all artifacts using the DoW OIG tool of choice such as MS Teams and SharePoint. Ensure artifacts are linked and leverage object reuse where possible to ensure accurate system models for DoW OIG programs.
1. Gather systems requirements, develop the architecture, design, integrate and test software modules and field the software for use by the DoW user community.
1. Design, develop, test, install and document all currently deployed changes to the system Baseline Configuration in accordance with the Implementation Plan. The system will expand upon current capabilities and provide scalability for future growth.
1. Provide cost estimates and/or benefits of current and alternate system design implementation, identifying required artifacts and advising the DoW OIG accordingly.
Task 5.1.6 System Design
| Performance Standard |
| AQL |
| Surveillance Method |
| System Design |
| Performance/Deliverables: |
~ Architecture Views, Diagrams, and Artifacts (as required) ~ Implementation Plan Inspection of delivered materials.
| Task Elements: a) – k) |
| Contain required information, 90% accurate/error free, and delivered on time. |
Any required revisions are:
5.1.7 Subtask 1.7 – Configuration, Change Management, and Deployment Configuration, change management, and deployment support are required to effectively plan, document, manage, and implement the changes required to maintain and modernize DoW OIG systems and environments. A configuration management (CM) program is required, complete with management tools, processes, and procedures that are designed to account for the OIG systems and environments, their configuration, and deployment plans. As system features are developed and infrastructure options become available, implementation assistance is essential to apply updates and/or upgrades necessary to ensure continued operations of OIG systems.
The Contractor shall:
1. Create and maintain configuration baselines supporting developmental and operational systems. Recommend CM tools and implement CM policies and procedures. Develop and modify CM plans, policies, and procedures tailored to support developmental or operational systems.
1. Propose changes that improve the current system configuration and submit it for approval to the Configuration Control Board (CCB). Document all baselines, Change Requests (CRs), deviations, and waivers.
1. Establish a formal CM program that addresses all new and modified hardware, firmware, software, and documentation resulting from the contract. The CM program shall include a CCB consisting of representatives from Contractor, DoW OIG, and external entities. The CM program shall provide configuration identification, configuration control, and configuration status accounting of all new or modified hardware, firmware, software, and documentation including Government Furnished Property for the duration of the contract.
1. Establish formal software development, code control, and build processes for major and minor (patches) releases and full integration. Establish and maintain documentation to include, but not limited to, system and application versioning and changelogs.
1. Establish and maintain a Configuration Control Plan, adhering to configuration control standards for any changes, only enacting approved system changes in accordance with each PMO. Submit CRs to the CCB for evaluation, prior to implementation. Identify and track changes and update system and design documentation within 15 days of changes being implemented.
1. Identify system changes that impact system documentation, notifying relevant parties that updates are required.
1. Develop a plan to guide production deployment. The deployment plan shall detail the approach and schedule for migration of objects from the testing environment to production and modifications to production.
1. Provide a proposed implementation plan to deploy capabilities to the workforce.
1. Plan for deployments, patches, upgrades, fixes, enhancements, software and hardware change verifications and releases in accordance with the Government-approved deployment plan.
1. Develop operational documentation in preparation for deployment.
1. Coordinate deployment plans with DoW OIG and system user communities.
1. Utilize industry best practices for migration and deployment support and identify any improvement areas.
1. Build and provide Technical Data Packages for supported systems bi-annually.
Task 5.1.7 Configuration, Change Management, and Deployment
| Performance Standard |
| AQL |
| Surveillance Method |
| Configuration, Change Management, and Deployment |
| Performance/Deliverables: |
~ Configuration Control Plan (due 30 days after start) ~ Technical Data Packages (bi-annually) Inspection of delivered materials.
| Task Elements: a) – m) |
| Contain required information, 90% accurate/error free, and delivered on time. |
Any required revisions are:
5.1.8 Subtask 1.8 – Test and Evaluation
Test and evaluation are required to maintain reliability, availability, and maintainability standards in accordance with application uptime, quality, and performance requirements.
Support includes unit, regression, load and stress, interoperability and integration, and user acceptance testing - tailored across each application. Validation of testing results and identification of efficiencies is also required.
The Contractor shall:
1. Establish and maintain a test and evaluation master plan.
1. Identify discrete units prior to unit testing and test each unit thoroughly before deployment.
1. Design and execute unit test scripts to test all system modules and interfaces that correlate to all in-scope requirements, gaps, enhancements, and design modifications.
1. Perform unit testing to identify issues and defects and ensure all necessary activities and fixes have been executed and recorded before delivery of applications for Government functional testing.
1. Provide test plans that demonstrate that each requirement and business rule has been addressed in the design to be tested.
1. Provide test reports, organized by module, identifying each test scenario/function and include pass/fail…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .