CAMIS PWS_RFI.docx

PERFORMANCE WORK STATEMENT (PWS) OFFICE OF NAVAL RESEARCH (ONR)

CONTRACT/GRANT AWARD MANAGEMENT INFORMATION SYSTEM (CAMIS)

MAINTENANCE AND SUPPORT SERVICES

1.0 SCOPE OF WORK

The Contractor shall provide systems engineering and technical assistance support services for the CAMIS system and its related applications and interfaces. The scope of this task order is limited to the following performance areas, detailed in the subsequent sections:

· Area 1: Program Management and Governance

· Area 2: Application and System Development

· Area 3: Operations and Maintenance

· Area 4: Information Assurance & Compliance

· Area 5: Training and Documentation The Contractor shall provide all services in accordance with the metrics identified in the IDIQ SOW and the Quality Assurance Surveillance Plan (QASP).

1.1 Supported Systems and Applications

Application Purpose Software*

CAMIS Used by ONR Code 24 for data entry and display of award-related information. All of ONR also use it to run various reports.

The CAMIS application runs on the Microsoft .NET framework, Windows Server, Internet Information Services, Oracle Database, and RedHat Linux server. Utilizing Common Access Card for user authentication.

External Interfaces

The current system manages external data exchanges through four primary interface methods, utilizing EDI, XML, and system-call protocols to transfer procurement, invoicing, and closeout data.

To execute and manage these external data transmissions, the architecture leverages a combination of enterprise application software, integration middleware, and automated data transfer protocols. The system interfaces directly with enterprise-level procurement platforms, notably the

1. Inbound Procurement Data (PPS to CAMIS)

· Source System: Procurement for the Public Sector (PPS)

· Target System: CAMIS

· Data Type: Grants award and modification data

· Transmission Method: Electronic Data Interchange (EDI 850 / 860)

2. Inbound Invoicing (WAWF to CAMIS)

· Source System: Wide Area Workflow (WAWF)

· Target System: CAMIS

· Data Type: Vendor invoices for processing

· Transmission Method: XML Interface

3. System Pulls & Document Integration (DLATS/GEX & Aggregators)

· Mechanism: System calls and data pulls via Defense Logistics Agency Transaction Services (DLATS) and Global Exchange Service (GEX).

· Data Type: PDF files and associated metadata transferred into the successor electronic file system.

· Data Sources: * PIEE Enterprise Modules: Electronic Data Access (EDA) and Enterprise Award File.

· Data Aggregators: ADVANA or equivalent platforms.

4. Outbound Contract Closeout (System to DLATS/GEX)

· Source System: CAMIS / Core System

· Target Systems: Loaded into Electronic Document Access (EDA) and Federal Procurement Data System -

SAP Supplier Relationship Management (SRM) Procurement for Public Sector (PPS) module for contract and grant initiation, and the Defense Logistics Agency (DLA) Transaction Services gateway framework. Data parsing, validation, and transformation are handled via specialized middleware engines; Electronic Data Interchange (EDI) translators process inbound and outbound ASC X12 transaction sets (specifically 850, 860, and 567C), while native XML parsers and Web Services facilitate the ingestion of structured invoice schema from the Wide Area Workflow (WAWF). Document management and automated metadata synchronization are supported by secure File Transfer Protocol (SFTP) daemons and Application Programming Interfaces (APIs) embedded within the Global Exchange Service (GEX) and the Procurement Integrated Enterprise Environment (PIEE). Furthermore, big-data platform connectors and advanced database drivers are utilized to orchestrate downstream extraction and aggregation pipelines with successor file systems and central repositories like ADVANA.

Next Generation (FPDS-NG) via DLATS/GEX.

· Data Type: Contract closeout and completion data

· Transmission Method: X12 Transaction Set EDI 567C (Contract Completion Status)

4. Additional File Support Systems

· Source System: External / Core System

· Target Systems: CAMIS

· Data Type: varying

· Transmission Method: API or other direct transmission method

*Government may elect to change software during the period of performance.

2.0 PROGRAM MANAGEMENT, GOVERNANCE, AND ANALYSIS

The Contractor shall provide comprehensive program management, agile coordination, and contract oversight to ensure all activities performed under this PWS are executed on time, within budget, and in accordance with Navy standards..

2.1 Project Management: The Contractor shall manage the performance and completion of projects from concept to completion through a Government-designated Product Backlog and prioritization process, as set out in Section 3, below. This includes developing detailed work plans, schedules, resource plans, and status reports. The Contractor will conduct project meetings, track progress, and provide analytical guidance to the project team.

2.2 Strategic Support & Systems Analysis: The Contractor shall assist ONR with researching new business practices, analyzing management information requirements, and advising on the potential benefits of automation to improve efficiency. This includes performing business and systems analysis to elicit, validate, and translate approved user requirements into actionable technical specifications and user stories, and measurable acceptance criteria. The Contractor shall maintain traceability between approved business requirements, user stories, development activities, testing, releases, and Government acceptance throughout the software development lifecycle.

2.3 Agile Project Management: The Contractor shall manage all Agile project development activities, including daily scrums, review/retrospective meetings, sprints, and release activities. The Contractor shall maintain the Agile project schedule, product backlog, and work item status within the Government-designated Azure DevOps environment

2.4 Stakeholder Engagement: The Contractor shall represent ONR CAMIS program in meetings with internal and external stakeholders (e.g., DFAS, DISA, DoD activities) and serve as the single point of contact for assigned projects. The Contractor shall attend all scheduled and ad hoc meetings as required by the COR

2.5 Contract & Risk Management: The Contractor shall monitor project health, manage contract deliverables (Exhibit A), manage risks and issues, and provide regular status and financial reporting to the COR.

3.0 APPLICATION AND SYSTEM DEVELOPMENT

The Contractor shall employ an Agile software development methodology using iterative, time-boxed sprints to develop, enhance, test, document, and maintain the CAMIS application. The Government shall identify, prioritize, and manage business requirements within the Government-designated Product Backlog, generally at the Epic and Feature levels or equivalent work-planning constructs. The Contractor shall refine approved business requirements into implementable User Stories containing technical tasks, acceptance criteria, and supporting implementation details necessary to complete the work. Backlog refinement, sprint planning, development, testing, demonstration, and retrospective activities shall be performed throughout the Period of Performance to support continuous delivery and incremental system improvement.

Once Sprint Planning has concluded, the Sprint Backlog shall remain stable to the maximum extent practical. Government-directed additions, removals, or reprioritization of work during an active sprint may require reassessment of sprint scope, schedule, planned work, or completion of previously committed User Stories. The Contractor shall evaluate the operational and technical impacts of such changes and communicate the anticipated effects on sprint commitments to enable the Government to make informed prioritization decisions.

3.1 Business and Systems Analysis:

The Contractor shall perform detailed analysis of CAMIS processes and user workflows. Tasks include:

· Eliciting, validating, and documenting user requirements and translating them into developer-ready user stories, functional specifications, and acceptance criteria.

· Acceptance criteria shall be developed for each User Story in collaboration with the Government, documented in the Government-designated backlog. Work may not proceed without Government approval.

· Conducting gap analyses on legacy processes to identify automation and modernization opportunities.

3.2 System Development:

The Government shall maintain ownership of the Product Backlog at the “Epic” and “Feature” levels and shall prioritize those items. The Contractor shall decompose approved Epics and Features into user stories and technical tasks and determine engineering approach, task sequencing, and assignment of qualified personnel. The Contractor may recommend changes to priority based on dependencies, risk, or efficiency. Development includes improvements and new elements for:

· User interface, front end, and design schema.

· Application features, processes, programming, components, etc.

· Interfaces with existing or new systems.

· Reports, data visualizations, and business intelligence integrations.

· Database(s), system architecture, and network connections (including the creation and maintenance of Entity-Relationship Diagrams (ERDs) and system architecture diagrams).

· User management and access controls.

· All testing, verification and validation of operability.

3.3 New Capabilities and Advanced Technologies:

The Contractor shall program all coding for new and approved enhancements, additional features, and advanced capabilities, ensuring full functionality, optimal performance, and strict adherence to security protocols. The Contractor shall design, develop, and integrate modern technical solutions, which may include but are not limited to:

· Artificial Intelligence (AI) & Machine Learning (ML): Development and integration of predictive models, automated decision-support tools, and data-driven algorithms.

· Generative AI & Natural Language Processing (NLP): Implementation of secure, approved large language models (LLMs) for automated text summarization, semantic search, document interrogation, and conversational assistance.

· Intelligent Automation: Creation of robotic process automation (RPA) and automated workflows to reduce manual overhead.

· Data Analytics & Advanced Visualization: Implementation of predictive analytics, interactive dashboards, and business intelligence features. All AI/ML capabilities developed under this task order must comply with applicable Department of War AI ethical principles, verification standards, and secure deployment frameworks on authorized networks.

3.4 Technical Documentation & Process Mapping

Alongside software development activities, the Contractor shall develop, maintain, and update technical documentation and information design artifacts that support the design, development, testing, deployment, operation, maintenance, and long-term sustainment of the CAMIS application and its supporting infrastructure. Such documentation consists of technical work products intended to improve system maintainability, usability, knowledge transfer, and compliance and is distinct from contractual CDRL requirements unless specifically identified as a CDRL deliverable. The Contractor shall draft, edit, maintain, and update these artifacts, prioritized within the Government-designated Product Backlog consistent with overall program priorities, to support the Government’s operational, technical, and programmatic objectives. Tasks include:

· 3.4.1 Process Mapping & Visual Workflows: The Contractor shall develop and maintain visual workflows that bridge business requirements and technical execution. This includes:

· Creating and updating Business Process Modeling Notation (BPMN) diagrams, user journey maps, and operational system workflows (both As-Is and To-Be states).

· Designing system architecture, data flow diagrams (DFDs), and integration path layouts.

· 3.4.2 User-Facing Materials: The Contractor shall draft and maintain accessible, clear, and plain-language documentation to support the end-user community. This includes:

· Step-by-step user guides, quick-reference sheets, and online help-center content.

· Standard Operating Procedures (SOPs), training aids, and executive briefings.

· 3.4.3 Technical Artifacts: The Contractor shall deliver and maintain structured technical documentation to support system administrators, external interfaces, and audit readiness. This includes:

· System Administration Guides, Technical Design Documents (TDDs), Interface Control Documents (ICDs), and Release Notes.

· Maintaining precise inline code documentation and updating schema/database configuration logs for system maintainability.

· 3.4.4 Compliance and Quality Standards: The Contractor shall ensure that all written and visual deliverables are logically structured, plain-language compliant, and strictly adhere to Section 508 accessibility standards for electronic and information technology.

· 3.4.5 Documentation Prioritization: Documentation deliverables shall be developed as directed and prioritized within the sprint backlog. The Government and Contractor shall identify the documentation artifacts required for each approved enhancement, release, or development effort during backlog refinement, release planning, or other Government-approved work planning activities.

4.0 OPERATIONS AND MAINTENANCE

The Contractor shall perform all maintenance and support efforts to ensure existing functionality and ongoing operations. All efforts will be prioritized by the Contracting Officer’s Representative (COR).

4.1 System Maintenance

· 4.1.1 Application and Database Maintenance: The Contractor shall update, maintain, and support the delivered software for CAMIS. This includes streamlining the database, altering procedures, optimizing performance, and resolving issues. The Contractor shall document all changes to software, architecture, and business processes.

· 4.1.2 Server and Browser Updates: The Contractor shall provide maintenance for required application server (e.g., Windows Server) and browser (e.g., Firefox, Chrome, Edge) updates. This includes programming and testing all changes to ensure proper functionality, security, and Section 508 compliance.

· 4.1.3 Regulatory Compliance: The Contractor shall maintain the software to ensure business rules and processes remain current with federal regulations, including FAR, DFARS, NMCARS, OMB Circulars, and DODGARs.

4.2 Interface Maintenance

The Contractor shall maintain, monitor, and troubleshoot all CAMIS interfaces to ensure transactions are processed as expected.

· CAMIS EDI/XML Invoice (WAWF): Maintain the interface with WAWF, coordinate with stakeholders (DFAS, DISA), and make modifications when transaction requirements change.

· CAMIS EDI Award (850/860): Maintain the award receipt module, coordinate with Navy ERP and other originators, and modify business rules as needed.

· CAMIS EDI 567C (Contract Closeout): Maintain the contract completion status interface, coordinate with stakeholders, and ensure transactions are properly sent to EDA.

· File Support Systems (FSS): Support connections to FSS, including downloading EDA documents, testing interfaces, and assisting OCIO with FSS-related changes affecting CAMIS.

4.3 Hybrid User Support & Application Analysis

The Contractor shall utilize a hybrid support model where user assistance, issue triage, and resolution are conducted by personnel functioning as both system analysts and application developers. Personnel assigned to these hybrid support responsibilities may also perform software development, business analysis, database administration, testing, and user support functions. The Contractor shall determine the day-to-day assignment of qualified personnel based on the prioritization and nature of work components, operational urgency, and approved development schedules. This integrated approach ensures that user issues are analyzed and addressed by subject matter experts while supporting continuous system improvement. Scaled-Down Triage and Queue Management: The Contractor shall provide support services during core business hours (0800 to 1700 ET, Monday through Friday, excluding federal holidays).

· To allow analysts/developers to balance user support with active agile sprints, support will be primarily asynchronous and managed via the approved ticketing system (e.g., Remedy).

· Functions include monitoring the ticket queue, performing root-cause analysis on user-reported issues, resolving data or user-error issues directly, documenting troubleshooting activities, and translating systemic bugs or feature requests into the agile development backlog for Government prioritization.

· Initial Response (SLA): Acknowledge and log all support requests within four (4) business hours. Requests received after hours/holidays must be acknowledged within the first two (2) business hours of the next business day.

· Ticket Processing: Maintain detailed logs of all troubleshooting and communication inside the ticket. Process and resolve tickets based on Government-established mission priority (Critical, High, Medium, Low) rather than chronological order; priority shall be assigned in accordance with definitions and criteria in the QASP.

· Unresponsive User Closure: The Contractor is authorized to close a ticket if a user fails to respond after three (3) documented contact attempts.

· Escalation & Holds: Issues requiring software modifications, database changes, or new functionality shall be documented and coordinated with the COR for prioritization within the agile development backlog. The Contractor shall immediately escalate confirmed incidents and notify the COR as soon as practicable. Changes to backlog priority or diversion of support/direction from sprint work may be necessary.

· Tickets actively awaiting user feedback, Government decisions, system access, external-agency action, or COR approval shall be placed "On Hold" to pause the applicable response timeline.

· The labor categories identify the capabilities required to perform the work. Qualified personnel may perform work across compatible functional areas, provided they meet the qualifications applicable to the work performed. The Contractor remains responsible for providing all capabilities required under the contract.

4.3.1 Developer-Led Response Times:

Initial review, response, and categorization of user tickets shall occur within 4 business hours.

· Critical system outages or immediate work stoppages shall be escalated and addressed immediately.

· Routine incidents, non-critical bugs, and minor enhancement requests will be evaluated by the analyst/developer and scheduled into appropriate development cycles based on COR prioritization.

4.3.2 Systems Analysis and Customer Guidance: Acting as Subject Matter Experts (SMEs), the hybrid team shall guide users through complex workflows, investigate data anomalies, and actively identify opportunities for user interface (UI) or business logic improvements based on recurring support trends.

4.3.3 Ad Hoc Data Analysis and Queries: The Contractor shall leverage their development and database expertise to perform complex ad hoc data queries, extract insights, and generate custom reports from the CAMIS database as directed by the COR. Requests shall be documented in the Government-designated backlog and prioritized against other authorized work.

5.0 INFORMATION ASSURANCE & COMPLIANCE

The Contractor shall assist ONR with all activities necessary to maintain the system’s Authority to Operate (ATO).

5.1 IA Sustainment: The Contractor shall perform routine activities to sustain the IA certification under the Risk Management Framework (RMF), including testing, documentation, and remediation.

5.2 Compliance Requirements: The Contractor shall support and provide documentation for all compliance activities, including but not limited to: DITPR-DON, DADMS, FISCAM, NIST guidelines, FISMA, FIAR, and STIG.

5.3 IAWF Training and Certification: All Contractor personnel must have the proper and current Information Assurance (IA) certification in accordance with DoD 8570.01-M. The Contractor shall provide documentation of certification status and notify the COR 90 days prior to any certification expiration.

6.0 TRAINING AND DELIVERABLES

6.1 Training: As required, the Contractor shall provide training to end-users for CAMIS system updates or changes. Training materials may include system documentation, diagrams, user guides, and training videos.

6.2 Deliverables: The Contractor shall provide the eleven (11) data requirements as listed in Task Order Exhibit A.

All contractor personnel proposed and utilized under this Task Order, regardless of labor category, seniority level, or key personnel status, shall meet and adhere to the following baseline qualifications and professional standards.

These requirements are in addition to, and do not duplicate, the specific education, experience, and technical certifications listed in the individual labor category profiles:

· Citizenship and Security Clearance: Every member of the contract team must be a United States Citizen and maintain an active, fully adjudicated Secret security clearance at the time of proposal submission, award, and throughout the entire period of performance.

· Personnel may be brought on board, at the COR’s discretion, with an Interim Secret security clearance while their clearance is adjudicated.

· Office Automation Proficiency: All personnel shall be highly proficient and experienced in utilizing the Microsoft Office 365 suite, to include but not limited to Microsoft Word, PowerPoint, Outlook, SharePoint Online, Teams, and Excel, to execute daily tasks and collaborate.

· Professional Communication Standards: All contractor personnel are required to demonstrate professionally polite, proficient, and effective verbal and written communication skills. All official communications—whether with government stakeholders, end-users, or teammates—must be entirely void of slang, colloquialisms, and/or phrases that could be interpreted as vulgar, offensive, or unprofessional.

· Operational Independence and Collaboration: Team members must demonstrate the ability to work highly effectively both independently (without requiring constant government oversight) and collaboratively in a cross-functional Agile team environment.

· Meeting Facilitation: Personnel must possess the organizational skills necessary to schedule, organize, and coordinate virtual or in-person meetings, to include preparing agendas, managing invitations, and documenting clear action items.

· Professional Judgment: All personnel shall demonstrate creativity, foresight, professionalism, and mature judgment in anticipating, identifying, and addressing complex scientific, business, financial, or program management tasks associated with their respective roles.

/ Programmer (.NET)

/ Programmer (.NET)

Security+ CE).

.NET framework, Entity Framework, Git, RESTful APIs, AI-assisted coding tools (e.g., GitHub Copilot if IL5 approved). Soft: Collaborative problem-solving, fast-paced adaptability. Admin: Daily ticketing updates, Jira board maintenance.Cert: DoD 8140/8570 IAT Level II.

/ Engineer

Tools: Oracle Enterprise Manager, AI-driven DB performance tuning.Soft: Analytical problem-solving, communicating data risks.Admin: Maintaining data dictionaries, schema versioning.Cert: Oracle DB Cert preferred; DoD 8140/8570 IAT Level II required.

Report scheduling, tracking query requests.

ACAS/Nessus scanning, Fortify/SonarQube (code security), AI-assisted vulnerability analysis. Soft: Collaborative compliance enforcement. Admin: Maintaining POAMs, organizing audit artifacts. Cert: DoD 8140/8570 IAM Level II or IAT Level III.