Deadline Date: Wednesday 6 November 2024

Requirement: Atlassian Confluence Federation and Replication Mechanism Proof Of Concept

Location: Off-Site (The travel expenses for Site Acceptance Test in SHAPE, Mons Belgium shall be included in the bid)

Note:Please refer to your Subcontract Agreement, article 6.4.1.a, which states “Off-Site Discount: 5% (this discount is applicable to all requirements, and applies when the assigned personnel are permitted to work Off-Site, such as at- home)". Please be sure to price this discount in your overall price proposal when submitting bids against off-site RFQs

Period of Performance: As soon as possible but not later than 04 December 2024 until 30 June 2025

Required Security Clearance: NATO RESTRICTED

1. Bidding Instructions:

1.1. Technical Proposal

Bidders shall submit a proposal clearly providing the following information:

a. The proposed approach to address the required scope of work and the required delivery and milestones plan.

b. CVs and Attestations of the assigned resource(s) for the project. It is up to the bidder to propose the size of the team that executes the work and produces the deliverables in the timeline allocated.

c. A compliancy matrix clearly stating how your proposal meets the deliverables/ performance goals outlined in Part 2, Section 2.

d. Any other appropriate technical information to determine whether your proposal meets the deliverables/ performance goals outlined in Part 2, Section 2.

e. Any other similar past performances explaining the relevance of the bidder with the requirements and elaborating on why they are the best candidate for this contract award.

2. Award

The contract shall be awarded under the framework contract CO-115786-AAS+ - Market Place 1.

1. INTRODUCTION

The NCI Agency has been established with a view to meeting the collective requirements of some or all NATO nations in the fields of capability delivery and service provision related to Consultation, Command & Control as well as Communications, Information and Cyber Defence functions, thereby also facilitating the integration of Intelligence, Surveillance, Reconnaissance, Target Acquisition functions and their associated information exchange.

The NATO Cyber Security Centre (NCSC) is a team of over 200 members working to monitor and protect NATO networks. In the NCSC’s role to deliver robust security services to the NATO Enterprise and NATO Allied Operations and Missions (AOM), the centre executes a portfolio of programmes and projects around 219 MEUR euros per year, in order to uplift and enhance critical cyber security services. The Portfolio ranges from Programme of Work (POW) activities funded via the NATO Military Budget (MB) to Critical / Urgent Requirements (CURs/URs) and NATO Security Investment Programme (NSIP) projects funded via the Investment Budget (IB). In some edge cases, projects are also funded via the Civilian Budget (CB). Projects can span multiple years and are governed by various frameworks, including the Common Funded Capability Development Governance Framework (CFCDGM).

In order to execute this work, the NCI Agency is seeking for expertise to develop a replication mechanism between 2 Atlassian confluence instances responding to all the requirements (technical and functional) captured in the chapter 3 “Requirements” below and the associated Annex A. These 2 instances cannot directly communicate with each other.

2. DELIVERABLES

D1. The contractor shall demonstrate the technical concept to achieve the requirements laid out in the Statement of Work

D1 Outcome: An approved technical concept for implementing the solution

D2. The contractor shall demonstrate in a test environment the technical implementation of the replication mechanism for new content, being a space or a page.

D2 Outcome: The demonstration is confirming that the solution is able to transfer a confluence page or a confluence space from one environment to the other environment.

D3. The contractor shall demonstrate in a test environment the technical implementation of the replication mechanism for handling update and deletion of existing content.

D3 Outcome: The demonstration is confirming that the solution is able to replicate update or deletion of confluence page or a confluence space from one environment to the other environment.

D4. The contractor shall demonstrate the solution is able to handle exceptions and errors, and that the logging mechanism for troubleshooting is meeting the requirements. The solution will include safeguards to prevent the failure of the content to be replicated and what has been replicated

D4 Outcome: The demonstration is confirming that the solution is able to handle exception and errors, and provide the level of logging appropriate to a Confluence administrator to handle the error and rectify the error. The safeguarding mechanism will have to be demonstrated.

D5. The developed solution is passing the Site Acceptance Test and delivered to NCSC.

D5 Outcome: A fully working (as per chapter “3. requirements” below and associated “Annex A - detailed technical requirements for implementation”) replication mechanism of Atlassian Confluence, implemented on a test environment and delivered to NCSC on a collection of virtual machines in VMWare format, with full access to all content and developed

D6. The contractor shall fully document the solution and the development code associated. The ownership and copyright of the code shall become the property of the NATO Communications and Information Agency.

D6 Outcome: A documentation, in Atlassian Confluence format covering: A high level design of the solution; A detailed design of each component of the solution; An administration and troubleshooting documentation; Extensive source code documentation allowing for maintenance and improvements

3. REQUIREMENTS

3.1 DATA REPLICATION REQUIREMENTS:

1. The solution should take a form of plugins for Atlassian Confluence.

2. The plugins shall work in DataCenter edition of Confluence environment in the versions currently installed on NCSC networks on the day of awarding the contract. (8.5.12 LTS)

3. The underlying operating system is Red Hat Enterprise Linux 9 (RHEL 9)

4. The 2 Confluence instances cannot communicate directly. Each instance can access a dedicated Samba network share to write or read files.

5. The content shall be transferred as encrypted files using public private (PKI) keys (at no time the content outside Confluence can be unencrypted)

6. Solution shall work with NCSC delivered pairs of certificates and private keys.

7. Solution shall allow for changing the certificates and associated private keys as often as needed from the user interface or command line interface on the servers without any need to recompile or change the code

8. Encryption and decryption as well as export and import methods should be exposed as REST Endpoints methods for allowing some ad-hoc script-base troubleshooting and fixing

9. Solution should automatically check validity of certificates using base on the certificate CDP (CRL Distribution Point) CRL or OCSP.

10. The replication will occur only one way

a. Shall allow defining the Replication Partners with associated certificates

b. Shall allow to configure the plugin to be the exporting or importing node.

c. Shall have all its configuration parameters available and modifiable on the web interface of the plugin within Confluence.

d. Shall allow for independent definition of the landing zone (network share) for export purpose and pick up zone (network share) for import purpose. The network share will be accessed using protocol Microsoft SMB version 3.

e. Shall replicate all of the data in destination partner exactly as it is presented in the source partner, in the correct chronological order, that includes all data, comments, workflows’ states, timestamps, attachments, users, spaces, update history, graphics, embedded elements (including objects from other plugins, e.g. Gliffy for Confluence), links, etc.

i. In case the user is missing the new user of the same name shall be created. It shall be deactivated. User creation shall be logged.

ii. User group ownership and associated Role-Based Access Control (RBAC) shall be respected.

iii. The newly created user needs to belong to equivalent groups of those to which the original user belonged. If any of the group do not exist it has to be created with the same name and it needs to belong to equivalent groups to those which source group does (Nested Groups).

iv. Tracking of any problem in the replication mechanism will be tracked in an automatically generated Atlassian JIRA issue.

v. Every replicated object/content will indicate its originator partner.

f. Shall allow for defining which elements to be replicated from the source to the destination partner.

g. Shall indicate for each page the originating network, and make the page read-only.

h. Any change to the above elements shall trigger delta replication

i. Links and custom fields IDs shall be translated in consistent way to prevent breaking the links in the content

j. On the destination partner there shall be periodically scheduled job to check if a synchronization file appears in the pick-up zone. Frequency of the checks shall be customizable. If there are multiple replication files present the job should trigger the import in order of files creation timestamps.

11. All functions shall be configurable from User Graphics Interface in Confluence.

12. Solution shall use native JIRA & Confluence mechanisms as much as possible

13. Solution shall have extensive logging capability with defined at least levels of logging to allow audits and troubleshooting. Logs shall be stored in dedicated log files. Logs shall be in structured format and human-readable (JSON, XML,…)

14. Solution shall provide exact replication of the information from the source system.

15. Further detailed technical recommendations for implementation are part of Annex A.

3.2 SUPPORT TESTING AND VALIDATION REQUIREMENTS:

Solution Acceptance Test (SAT) is to be conducted on NCSC test environment prior the implementation on the operational environment

Above activities shall be supported on NCSC premise by the contractor.

3.3 DOCUMENTATION REQUIREMENTS:

Language: the product shall be written in English, meeting the NATO STANAG 6001 Level 3 “Professional Proficiency”.

Intended Audience: the product shall be intended for Cyber Security Professionals.

Accuracy: the product shall accurately reflect what was discussed, decided, and action items assigned during the meeting.

Clarity and Conciseness: Information shall be presented clearly and concisely, avoiding unnecessary jargon or complex language.

Formatting: Consistent formatting shall be used throughout the document, including font style, size, headings, and spacing further directed by the NCSC.

4. REPORTING

R1. On a biweekly basis, a videoconference shall be held to review the progress of the development of the solution and the state of the documentation of the solution

5. SKILLS

[See Requirements]

6. WORK EXECUTION

The development can be executed on any development environment.

Progress review meetings shall happen using videoconference at least once every 2 weeks.

Final testing (Site Acceptance Test) of the proof of concept shall happen on NATO premises (SHAPE, Belgium).

7. DELIVERABLES MILESTONES AND PAYMENT SCHEDULE

Payment will be done as per the milestones below and in accordance with the table below:

D1: 10 JAN 2025

Type and conditions of payment:  After approval of D1 by NCIA SDM and signed Delivery Acceptance Sheet

D2: 15 FEB 2025

Type and conditions of payment:  After approval of D2 by NCIA SDM and signed Delivery Acceptance Sheet

D3 15 MAR 2025

Type and conditions of payment:  After approval of D3 by NCIA SDM and signed Delivery Acceptance Sheet

D4 15 APR 2025

Type and conditions of payment:  After approval of D4 by NCIA SDM and signed Delivery Acceptance Sheet

D5 31 MAY 2025

Type and conditions of payment:  After approval of D5 by NCIA SDM and signed Delivery Acceptance Sheet

D6 30 JUN 2025

Type and conditions of payment:  After approval of D6 by NCIA SDM and signed Delivery Acceptance Sheet

The payment shall be dependent upon successful acceptance of the Delivery Acceptance Sheet (DAS) – (Annex B) including the EBA Receipt number.

Invoices shall be accompanied with a Delivery Acceptance Sheet (Annex B) signed by the Contractor and the project authority.

8. TRAVEL

All travel costs are included in the quoted price. No additional cost for travel (including accommodation, per diem, travel expenses, etc.,) will be claimed separately. All travel arrangements are the responsibility of the contractor.

9. PERIOD OF PERFORMANCE

The period of performance is as soon as possible but not later than 04 December 2024 and will end no later than 30 June 2025

10. SECURITY AND NON-DISCLOSURE AGREEMENT

Any contracted individuals of the Service Provider must be in possession of a security clearance by their National Authority of NATO RESTRICTED. The signature of a Non-Disclosure Agreement between any Service Provider’s individuals contributing to this task and NCIA will be required prior to execution.

Annex A – Detailed Technical Requirements for Implementation

1. Solution should provide a mutex mechanism per page that allows editing only on either Sender or Receiver instance.

a. Default should be that editing is allowed on the Sender side.

b. The switch for the mutex should be available for all users that have an Edit permission on specific page on the Sender side (not through the CTGUI).

c. The status of mutex shall be visible on bot Receiver and Sender sides

d. If mutex is set to allow editing on the sender side, editing in not allowed on the Receiver side and replication from the Sender to Receiver shall occur unless configured otherwise in CTGUI

e. When mutex is set to allow editing on the Receiver side it prevents any further editing on Receiver side unless mutex is switched back by admin (this actin shall be available only for the members of specific user group e.g. mutex-control-users). It also stops synchronization for this page.

f. Mutex mechanism shall not alter permissions in spaces or particular pages.

2. The Sender

a. CTGUI for Admins

b. shall be triggered by Confluence system Events (Event Listener)

c. Non-content events should be disregarded with the exception of Access Control Lists (ACL) changes

d. It shall be configurable per Space basis whether synchronization should occur or not with default action for the remaining spaces (default: not). All configurable from CTGUI

e. Information that shall be replicated fully (no change) consist of

• content

• its contributing users (collaborative editing in on for whole solution)

1. due to fact that users might have different names on both instances an exceptional translation table shall be established on the Receiver side

• and related timestamps

• or/and permissions changes

• mutex status

• ACL change

• AES 256 key (see below)

• Administrators gpg keys

f. Each event shall create an update file that will be sent to configurable from CTGUI Samba share

i. This update file shall be encrypted with AES 256 preshared key

1. This preshared key should be established every night at specific hour (configurable from CTGUI) and should consist on 40 random characters from the following set

• Small letters

• Capital letters

• ~!@#$%^_+=-`|\:”’;<>,.?/

2. The AES 256 key shall not be stored unencrypted in the DB, filesystem, etc.

• Unencrypted version only in memory

3. The key should be generated and encrypted with public key of the specific public private pair (gpg) of keys (upload-able through CTGUI) and replicated (via specific update file) to the Receiver at the specific time (point 1) where the Receiver will use the private key to decrypt it. Note that the Receiver shall store they AES 256 key in dedicated folder on the Confluence server (both Receiver and Sender) which should be encrypted with GPG with multiple recipients (plural, see reference link below). These gpg key for specific users (Administrators gpg keys) should be upload-able from CTGUI on the Sender side. The point of this is to allow advance troubleshooting for administrators.

4. Reference gpg mechanism’s link: https://www.gnupg.org/gph/en/manual/x110.html

ii. The update file should have a filename that contain a space, date-time timestamp and counter for ensuring data integrity on the Receiver side, e.g. MySpace_2024-01-01_00:00:000_0123

iii. Extension .sync

iv. There should be a mechanism in CTGUI that would allow manual trigger for regeneration and synchronization of the AES 256 key

v. There should be a mechanism in CTGUI that would allow to create an empty update file with specific metadata to allow fix missing update file.

g. There should be a mechanism, accessible through CTGUI which will allow for resending update(s) file manually to allow for possible troubleshooting using previous or current or manually provided AES 256 key and either keeping its/theirs original counters or shift them by set number.

h. There should be an option CTGUI to set counter (per Space) to arbitrary number.

i. All the update files shall be cached in dedicated Confluence server folder (CTGUI configurable) for certain amount of time (CTGUI configurable, default 2 weeks)

j. There should be an CTGUI page that would allow viewing and troubleshooting the update files cache.

3. The Receiver

a. CTGUI for Admins

b. Should be a scheduled job that can have different time triggers (crontab like) per space, configurable from CTGUI

c. It should look for update files in a CTGUI configured samba share (note: not the same as on the Sender side)

d. Base on character of the specific update file it should either establish new decryption or start synchronization

e. The job should establish a queue of updates per specific space and should control if updates are coming in order (see description of update file filename) and the required users exists on the instance

i. If there is a missing update file (next file already received) for configurable (CTGUI) amount of time (default 2 minutes) synchronization should pause on the Receiver side (new files shall still be queued). Email notification should be sent to predefined users (CTGUI) and warning banner should be displayed for them as well in the Confluence interface.

ii. There should be an option CTGUI that would allow to arbitrary set expected update file counter for specific Space.

iii. If there is a missing user on the Receiver instance synchronization should pause on the Receiver side (new files shall still be queued). Email notification should be sent to predefined users (CTGUI) and warning banner should be displayed for them as well in the Confluence interface

1. Due to fact that users might have different names on both instances an exceptional translation table shall be established on the Receiver side.

• Configurable on the CTGUI as one to one relation Sender username -> Receiver username

• This table shall be exportable and importable in both CSV and JSON formats

f. After the issue is resolved the synchronization should restart where it stopped processing queue updates.

g. All update files should be cached in dedicated folder (CTGUI configurable)

h. There should be CTGUI page that allow for troubleshooting cached update files and queues

i. It should allow for seeing the files, counter queues and alter their metadata in support of troubleshooting.

1. There should be an option to allow manual use of different (ad hoc provided) AES 256 key for allowing decrypting files that stuck due to some glitch during key change synchronization to be processed

i. Decryption mechanism and key synchronization was described in the Sender description.

j. Mutex as described earlier shall not change permissions on pages or spaces

k. ACL changes should perform the same checks as regular content updates with the same mechanism for control and troubleshooting.

l. Decryption synchronization mechanism and decryption itself errors should be reported the same way as content and ACL errors

m. In case that the required space does not exist on the Receiver side it shall be created exactly copying all the properties and attributes, timestamps, ACLs, etc. of the original one on the Sender side. User translation shall be applied in the process.

5. SKILLS

It is up to the bidding company to propose and size the team that will be working to fulfilling these deliverables.

Nevertheless, the person or team of persons working on this statement of work shall collectively (not for each individual) have the following skills:

• Intimate knowledge of the inner working of Atlassian Confluence at code and database level
• Mastery knowledge of ScriptRunner
• Mastery knowledge of using REST API and listeners
• Excellent knowledge of Linux operating systems
• Excellent knowledge of JAVA
• Excellent knowledge of Python

10. SECURITY AND NON-DISCLOSURE AGREEMENT

• Any contracted individuals of the Service Provider must be in possession of a security clearance by their National Authority of NATO RESTRICTED.

See more jobs at EMW, Inc.

Apply for this job

Deadline Date:Friday 8 November 2024

Requirement: Development and production of NCI Academy Course Control Documents (CCD)

Location: Oeiras, PT

Period of Performance:2025 BASE: As soon as possible but not later than 15/01/2025 – 31/12/2025 with the possibility to exercise the following options:

2026 Option: 01/01/2026 – 31/12/2026

2027 Option: 01/01/2027 – 31/12/2027

Start date is as soon as possible but not later than 15/01/2025

Required Security Clearance: NATO SECRET

1. INTRODUCTION

The NATO Communications and Information Academy (NCI Academy), located in Oeiras, Portugal, currently delivers NATO technical and operational training on a variety of hardware and software systems. All NATO approved and selected courses must have Course Control Documents (CCDs) as defined in chapters 5 and 6 of the Bi-SC Education and Individual Training Directive (E&ITD) 75-7, dated 10 September 2015. The CCDs are NATO’s mechanism to ensure responsiveness to NATO E&IT requirements.

The NCI Academy is looking to outsource the development and production of some CCDs for existing NCI Academy courses, and the maintenance updates of some existing CCDs. The intent is to obtain the services of subject matter experts who can develop and update CCDs. The Contractor shall make available personnel capable of providing the services specified in this Statement of Work (SoW).

The Contractor shall work in a multinational military/civilian staff environment and typically interact with different training experts and Section Heads to accomplish their tasks. Given the need for the incumbent to handle classified documentation, there is a requirement for a valid NATO SECRET Security Clearance as from contract start.

2. OBJECTIVE

Under the scope of work, the Contractor shall take the lead and work together with the NCI Academy Training Sections to develop or update, aligned with NATO regulations, the following documents for each designated course:

• List of Task Statements, incl. Performance/Task Statement Tracking Matrix

• Course Control Document I – Control Form;

• Course Control Document II – Course Proposal;

• Course Control Document III – Programme of Classes

3. SCOPE OF WORK

3.1 Tasking

3.1.1 The Contractor shall be responsible for developing NATO Course Control Documents as specified in paragraph 4 of this Statement of Work (SOW).

3.1.2 The Contractor shall adhere to the estimated deliverables and deadlines in paragraph 4 of this Annex. The Deliverables shall only be deemed delivered by the Contractor once approved by the Section/Branch Heads and the Quality Assurance Group (QAG) as appropriate.

3.1.3 In addition to the new CCDs Deliverables, the Contractor could be required to provide additional support and advice to maintain updates of existing CCDs, on a case-by-case basis, at the request of the Section/Branch heads, taking all circumstances and workloads into consideration. The NCI Academy will incur no additional costs for providing these services unless otherwise explicitly agreed upon by the contracting company and the NCI Academy.

3.1.4 The Contractor shall comply with the NCI Academy’s Standard Operating Procedures (SOP) when conducting work.(07.01.10 and 07.01.28),

3.1.5 The Courses CCDs covered under this agreement are the in the following areas:

1. C4ISR Technology (0101)

2. DCOI Level 1 Support Course (9065)

3. FAS Overview Course (9045)

4. AirC2IS courses

5. JADOCS courses

6. JTS courses

7. TOPFAS courses

8. NNMS courses

9. LOGFAS courses

10. MCCIS7 courses

11. NCOP courses

12. INTEL-FS courses

13. Core GIS courses

14. JOCwatch courses

15. NAMIS courses

3.2 Acceptance criteria

The deliverables shall only be deemed as completed by the Contractor once approved by the Section/Branch Heads and the QAG. The S/BH and QAG will have two weeks to review the deliverable and provide the feedback for final completion and acceptance of the deliverables, provided a mature deliverable is submitted for review. Acceptance will be done based on Annex B – Delivery Acceptance Sheet.

4. DELIVERABLES AND PAYMENT MILESTONES

4.1 Deliverables

The NCI Academy team reserves the possibility to exercise the described options, depending on the project priorities and requirements.

The payment shall be dependent upon successful acceptance of the Delivery Acceptance Sheet (DAS) – (Annex B) including the EBA Receipt number.

Invoices shall be accompanied with a Delivery Acceptance Sheet (Annex B) signed by the Contractor and line manager.

The following deliverables are expected:

01 Development of Task Statements, CCDs I, II, III for a 4-7days course (user or technical)

Effort in days (standard days 7.6 hrs): 10

Estimated Quantity/ iterations: 10

Payment Milestones: After the successful completion of the 3 course CCDs

02 Update of Task Statements, CCDs I, II, III for a 4-7days course (user or technical)

Effort in days (standard days 7.6 hrs): 7

Estimated Quantity/ iterations: 10

Payment Milestones: After the successful completion of the 3 course CCDs

03 Development of Task Statements, CCDs I, II, III for a 1 day course (user or technical)

Effort in days (standard days 7.6 hrs): 3

Estimated Quantity/ iterations: 3

Payment Milestones: After the successful completion of the 3 course CCDs

04 Update of Task Statements, CCDs I, II, III for a 1 day course (user or technical)

Effort in days (standard days 7.6 hrs): 2

Estimated Quantity/ iterations: 3

Payment Milestones: After the successful completion of the 3 course CCDs

05 Development of Task Statements, CCDs I, II, III for a 2 day course (user or technical)

Effort in days (standard days 7.6 hrs): 4

Estimated Quantity/ iterations: 3

Payment Milestones: After the successful completion of the 3 course CCDs

06 Update of Task Statements, CCDs I, II, III for a 2 day course (user or technical)

Effort in days (standard days 7.6 hrs): 3

Estimated Quantity/ iterations: 3

Payment Milestones: After the successful completion of the 3 course CCDs

Note 1: After the first course set of CCD completion, and upon Section/Branch Head agreement, the Contractor shall move to the second course set of documents following the same approach as with the first course set of CCDs.

Note 2: The deliverable should include the summary of identified training gaps and recommendations for continuous improvement.

Note 3: Price per iteration is all inclusive (including related travel costs, accommodation, per diem, etc.)

The payment shall be done after the successful completion of the 3 course CCDs, upon acceptance of the Delivery Acceptance Sheet (DAS) (Annex B) including the EBA Receipt number by the Purchaser. Invoice and DAS shall be provided to Purchaser for the payment of period of performance.

4.2 Expected Outcomes and Quality:

• Pre-meetings are conducted with Section/Branch Heads and Training Teams in order to define the most efficient and effective development approach for each set of Course CCDs, so that the end result is acceptable to them.

• The development and production of NATO Course Control Documents, as specified in paragraph 4 of this Statement of Work (SOW), a list of Task Statements that describe job performance, including the Performance/Task Statement Tracking Matrix. The CCDs must accurately, specifically, and completely capture the learning and performance objectives and supporting information (references, teaching points, timing, instructional strategy, presentation/activity, assessment strategy, etc.) for the existing NCI Academy courses.

• Whenever necessary, the Section/Branch Heads and Training Teams must be available, with one days notice, to clarify any doubts of the contractor that may arise during the execution of the tasks. Unless force majeur prevents this (e.g. sickness, accidents, death in the family etc.).

• The development and production of CCDs must follow the Bi-SC D 75-007 guidance and the CCD templates as mentioned in Annex H, K, L, and N of Bi-SCD 75-007

• The quality and completeness of the CCDs is sufficient to receive the Quality Assurance approval and the NCI Academy Dean’s signature and to be sent to the external stakeholders (such as the Department Head and the Requirements Authority of the Discipline and to ACT) for approval.

• If gaps and/or improvements are identified during the development of the CCDs, the contractor will document those gaps and/or improvements so that the NCI Academy can resolve the gaps and/or improvements before the CCDs are submitted to the external stakeholders.

4.3 Expected Performance:

4.3.1 Supervision: the contractor shall report to and receive technical guidance from a designated NCI Academy Official, who will serve as the Contracting Officer Technical Representative (COTR). The COTR (or appointed representative) shall provide direction, coordination, guidance, and support information, as needed, for all technical and content areas of the SOW. The COTR will:

• Resolve outstanding disputes, problems, deficiencies, and/or questions on the technical aspects of the SOW;

• Review (and approve) the contractor tasking and deliverables for completeness and accuracy.

4.3.2 The COTR will have weekly interaction with the Contractor and can assess their work's quality, quantity, and timeliness. He/She will review the Contractor’s work on a minimum of a bi-weekly basis or more often if needed.

4.3.3 The contractor shall agree, in advance, with the COTR on a plan of work, schedule, and necessary inputs and engagements to develop and complete the set of course CCDs and ensure that this plan is adhered to.

4.3.4 The contractor shall raise any issues, or blockers as soon as possible and inform the COTR if they require a change or deviation from the plan and schedule.

5. COORDINATION AND REPORTING

The Contractor shall coordinate each CCD delivery with the Section/Branch head, their designated representative, or COTR.

Work on development or updating the Course CCDs should only commence after the Section/Branch head has authorised it. The Section/Branch head and the NCI Academy QAG shall have at least two weeks to review and accept the updated CCDs material.

Weekly status report on progress on work is do be provided End of each week.

6. SCHEDULE

The task order will be active immediately after the signing of the contract by both parties.

It is expected that service will start not later than 15 January 2025.

7. CONSTRAINTS

All the documentation delivered under this statement of work shall be based on Annex K, L, and N of Bi-SCD 75-007 templates, the Academy SOP (07.01.10 and 07.01.28), and training documents provided in advance by the COTR.

All shall be stored under configuration management and in the provided NCI Agency IKM tools.

8. PRACTICAL ARRANGEMENTS

The contractor shall be required to work both on-site at the NCI Academy in Oeiras and at the customers’ sites.

Travel arrangements shall be the responsibility of the contractor and travel costs are included in the iteration price. The iteration price reflects 2 x Travel of 5 days duration during the period of the contract.

The contractor shall provide services under NCI Agency AAS contract for the NCI Academy in Oeiras, Portugal. He or she will work under the direction and guidance of the FS section head or their designated representative.

The NCI Academy will provide the service contractor with access to the Academy learning environment and business tools as required.

The Agency will provide the service contractor with a Reach laptop.

9. QUALIFICATIONS

[See Requirements]

10. SCHEDULE

This task order will be active immediately after signing of the contract by both parties. The BASE period of performance is as soon as possible but not later than 15/01/2025 and will end no later than 31/12/2025.

If the 2026 option is exercised, the period of performance is 01/01/2026 to 31/12/2026.

If the 2027 option is exercised, the period of performance is 01/01/2027 to 31/12/2027.

11. CONSTRAINTS

All the documentation delivered under this statement of work shall be based on NCI Agency templates or templates agreed with training section head.

All training material shall be stored in the provided NCI Agency tools.

All the deliverables of this project will be considered NATO UNCLASSIFIED.

Part of the work may involve handling classified networks, therefore, a security clearance at the right level is expected for the contractor(s) undertaking this service. This security clearance must be in place before applying for this contract to be considered compliant.

12. SECURITY

The security classification of the service will be up to NATO SECRET.

The contractor providing the services under this SOW is required to hold a valid NATO SECRET security clearance as from contract start.

9. QUALIFICATIONS

9.1 Essential Qualifications and Experience

The contractor should have the following qualifications:

• a Bachelor of Science (BSc) degree in Electronics Engineering, Computer Science/ Software Engineering/ Mathematics/ Electronics or related discipline at a nationally recognized/certified University, with 5 years post related experience, OR: a lower academic qualification combined with the demonstration of particular abilities or experience of relevance to this work, with a minimum of 8 years relevant experience.
• Substantial related experience within Quality Management / Instructional Systems Design / Change Management in an individual training and education environment
• Demonstrable experience with NATO Global Programming and the NATO systems approach to training (as described in Bi-SC Directive 75-7)
• Proven ability and results in developing and producing Course Control Documentation
• Recent experience in requirements analysis, designing courses and related Course Control Documentation
• Effective and excellent professional English language spoken and writing skills
• Experience in Microsoft Office
• Knowledge of NATO Education and Training Directives
• Ability to work in an International environment comprising both military and civilian elements

9.2 Desirable Qualifications/Experience:

• Experience working at a NATO Education and Training Facility or at ACT JFD E&T
• Prince2 Foundation
• Knowledge of the NCI Academy and NCIA
• Knowledge of NATO Quality Assurance Standards
• Experience working in NATO
• Experience in NATO Air Command and Control
• Experience with NATO Air C2 applications.

9.3 SECURITY CLEARANCE:

• The contractor providing the services under this SOW is required to hold a valid NATO SECRET security clearance as from contract start.

9.4 Language Proficiency:

• Level 3 English language skills according to NATO STANAG 6001: Listening (3); Speaking (2); Reading (3); and Writing (2) or according to Common European Framework of Reference for Language level B2-C1/Upper Intermediate-Advanced level

See more jobs at EMW, Inc.

Apply for this job

Deadline Date: Friday 8 November 2024

Requirement: NATO ICT role mapping support

Location:Off-Site

Note: Please refer to your Subcontract Agreement, article 6.4.1.a, which states “Off-Site Discount: 5% (this discount is applicable to all requirements, and applies when the assigned personnel are permitted to work Off-Site, such as at- home)". Please be sure to price this discount in your overall price proposal when submitting bids against off-site RFQs

Period of Performance: 2025 BASE: As soon as possible, but not later than 6 January 2025 – 31 December 2025 with the possibility to exercise following options:

2026 Option: 1 January 2026 until 31 December 2026

2027 Option: 1 January 2027 until 31 December 2027

Start date as soon as possible but not later than 6 January 2025.

Required Security Clearance: NATO SECRET

1. INTRODUCTION

At present, NATO does not have a standardized way to describe professional roles in the domain of Information and Communication Technology (ICT), nor are the Knowledge, Skills and Attitudes that are required to perform each of these roles successfully standardized.

Building on the previous year’s mapping of NATO Cybersecurity Roles, the aim of this project is to expand the mapping of all ICT roles to the SFIA Framework.

A 'NATO ICT Role' refers to a specific function within NATO that individuals occupy and execute. These roles are defined based on the SFIA framework, which serves as an industry-standard for standardizing language and categorizing skills. The scope of this mapping project includes all professionals in NATO who are involved in designing, developing, implementing, managing, and protecting the data and technology that power the digital world.

The project includes the creation of a database with all the acquired NATO ICT roles. The database will allow the identification of required trainings for each NATO ICT role and further analysis, for instance in supporting the forecasting of future training efforts.

2. OBJECTIVES

The scope of all activities is the NATO Enterprise unless otherwise indicated. At its conclusion, this project aims to deliver:

An inventory of all NATO ICT roles

A mapping of NATO ICT roles to the SFIA framework

A mapping of ‘Role to training recommendations’ for NATO ICT roles;

An implemented and accredited platform that enables hosting, analysing and managing all above mappings and creation of visual overviews and mapping reports per role, that can be used for insertion in / adjustment of NATO Job Descriptions (note: adjustment of the actual Job Descriptions is out of scope of this project)

3. SCOPE OF WORK in 2025

The following activities require support in 2025 under this SOW:

Where needed, finalize existing mappings, which focuses on NATO Cybersecurity roles and support the loading of these mappings in to the platform that was selected as Proof of Concept (Lexonis)

Build an inventory of NATO ICT roles and associated ICT Job Descriptions.

For all persona’s and 50% of all NATO ICT roles map the duties to the associated competencies and proficiency levels in the SFIA framework, create references to existing NATO and commercial training programs, and develop an annex and visual overviews to describe the SFIA mappings and training recommendations

Across all mapped NATO ICT roles: generate a cross-entity picture of ICT role training recommendations

Support the evaluation of the 2024 Proof of Concept of the mapping platform (Lexonis), pertaining to the platform’s ability to host, manage and analyse mappings, generate visual and usable reporting, identify required trainings for each NATO ICT role and further analysis, for instance in forecasting future training efforts and conducting competency assessments and function and to be accredited in the NATO IT system landscape, adhering to the associated security policies

Based on the evaluation outcomes, support the acquisition and/or implementation of the selected tool to host and manage all NATO CS and CSI role mappings to industry frameworks

Support the loading of all mappings between NATO ICT roles and industry frameworks to the selected platform

The contractor will work remotely, providing services during Core working hours of the NCI Academy team (Oeiras / PRT).

The measurement of execution for this work is sprints, with each sprint planned for a duration and due date as outlined in table 1 of Section 4 – Deliverables and Payment Milestones.

4. DELIVERABLES AND PAYMENT MILESTONES

The following deliverables are expected from the work on this statement of work:

2025 BASE: 01 January 2025 to 31 December 2025

Deliverable:  Up to 6 Sprints (Number of sprints is estimated considering a starting date of 1 January 2025. This will be adjusted depending on the actual start date.)

Payment Milestones: Upon completion of each sprint and at the end of the work.

The NCI Academy team reserves the possibility to exercise a number of options within the year 2025, based on the same scrum deliverable timeframe and cost, at a later time, depending on the project priorities and requirements.

The payment shall be dependent upon successful acceptance of the Delivery Acceptance Sheet (DAS) – (Annex A) including the EBA Receipt number.

Invoices shall be accompanied with a Delivery Acceptance Sheet (Annex A) signed by the Contractor and line manager.

See below for the schedule of 2025 deliverables:

Sprint 1: All missing mappings of NATO Cybersecurity roles from the 2024 PoW have been completed and validated and loaded on the platform that was selected as Proof of Concept (Lexonis) - 1 March 2025

Sprint 2: Evaluation finalized of the 2024 Proof of Concept of the mapping platform (Lexonis) + recommended way forward (i.e. accreditation of Lexonis OR explore other platform options) - 1 April 2025

Sprint 3: Up to 25% of all NATO ICT roles have been mapped to SFIA including training recommendations - 1 June 2025

Annexes and visual overviews have been developed to describe the SFIA mappings and training recommendations – Scope: 25% of all NATO ICT roles - 1 June 2025

All mappings of the 2024 project (focussing on NATO Cybersecurity roles) have been updated where needed - 1 June 2025

Sprint 4: Up to 50% of all NATO ICT roles have been mapped to SFIA including training recommendations - 1 Oct 2025

Annexes and visual overviews have been developed to describe the SFIA mappings and training recommendations – Scope: 50% of all NATO ICT roles - 1 Oct 2025

Overview of activities, work plan and engagement plan for the follow-on work in 2026 - 1 Oct 2025

Sprint 5: Across all mapped NATO ICT roles: generate a cross-entity picture of ICT role training recommendations - 1 Nov 2025

Sprint 6: All mappings between NATO ICT roles and industry frameworks have been loaded to the selected platform (depending on platform availability) - 1 Dec 2025

Final report describing the 2025 mapping outcomes - 1 Dec 2025

2026 OPTION: 01 January 2026 to 31 December 2026

Deliverable: Up to 6 sprints as described on above Table 1 section 4

Payment Milestones: Upon completion of each sprint and at the end of the work.

2027 OPTION: 01 January 2027 to 31 December 2027

Deliverable: Up to 6 sprints as described on above Table 1 section 4

Payment Milestones: Upon completion of each sprint and at the end of the work.

The NCIA team reserves the possibility to exercise a number of options in the respective option years, based on the same scrum deliverable timeframe and cost, at a later time, depending on the project priorities and requirements.

The payment shall be dependent upon successful acceptance of the Delivery Acceptance Sheet (DAS) – (Annex A) including the EBA Receipt number.

Invoices shall be accompanied with a Delivery Acceptance Sheet (Annex A) signed by the Contractor and the project authority.

5. COORDINATION AND REPORTING

The contractor shall participate in status update meetings, sprint planning, and other meetings, physically in the office, or in person via electronic means using Conference Call capabilities, according to line manager’s instructions.

For each sprint to be considered as complete and payable, the contractor must report the outcome of his/her work during the sprint, first verbally during the retrospective meeting and then in written within three (3) days after the sprint’s end date. The format of this report will be aligned with the line manager mentioning briefly the work held and the development achievements during the sprint.

Acceptance of each sprint completion will be documented in Annex A – Delivery Acceptance Sheet.

6. SCHEDULE

This task order will be active immediately after signing of the contract by both parties.

The BASE period of performance is as soon as possible but not later than 6 January 2025 and will end no later than 31 December 2025.

If the 2026 option is exercised, the period of performance is 01 January 2026 to 31 December 2026.

If the 2027 option is exercised, the period of performance is 01 January 2027 to 31 December 2027.

7. CONSTRAINTS

All the deliverables provided under this statement of work will be based on NCI Agency templates or agreed with the line manager.

All documentation will be stored under configuration management and/or in the provided NCI Agency tools.

All the deliverables of this project will be considered NATO UNCLASSIFIED.

Part of the work may involve handling classified networks, therefore, a security clearance at the right level is expected for the contractor(s) undertaking this service, although the contractor may start working already while the clearance process is ongoing.

8. SECURITY

The security classification of the service will be up to NATO SECRET.

The contractor providing the services under this SOW is required to hold a valid NATO SECRET security clearance

9. PRACTICAL ARRANGEMENTS

The work shall be primarily conducted remote, e.g. at the contractor’s premises, with occasional travel.

Travel costs are out of scope and will be borne by the NCI Agency separately in accordance to the provisions of the AAS+ Framework Contract. He or she will work under the direction and guidance of the NCI Academy Technical Capability Support Section Head or their designated representative.

10. QUALIFICATIONS

[See Requirements]

10. QUALIFICATIONS

The contractor should have the following experience:

Education:

• Master’s degree in Communications, Public Relations, Security related field, and/or multi-year experience doing Digital Transformation in an international environment, OR;
• Bachelor of Education/MSc degree in Human / Organizational Performance, OR;
• Bachelor of Science (BSc) degree in Electronics Engineering, Computer Science/ Software Engineering/ Mathematics/ Electronics or related discipline at a nationally recognized/certified University, with 5 years post related experience, OR:
• A lower academic qualification combined with the demonstration of particular abilities or experience of relevance to this work, with a minimum of 8 years relevant experience.
• Certification in ITIL 4 and/or Agile Project Management
• Demonstrable high level of Digital Literacy and a Cybersecurity certification

Experience:

• More than 6 years’ NATO experience in Education and Training, and more than 6 years’ industry experience in change management and Learning & Development related posts.
• Knowledge of / practical user experience with NATO Cybersecurity Education and Training design and delivery.
• Experience with mapping competencies to industry standard frameworks.
• Experience with mapping NATO specific Cybersecurity job roles to the NICE and SFIA frameworks and related training offerings.
• Experience with working with NCI Agency, NATO Support and Procurement Agency (NSPA) and NATO Enterprise entities (including the NATO Office of the chief Information Officer (OCIO).
• Experience with technical platforms to support competency based talent management / job role mapping (e.g. Lexonis).
• Demonstrable strong and recent existing networks in NATO ACT MDFD, NATO ACT CAP DEV, NATO SHAPE J6, NATO SHAPE J2, NCISG, NATO HQ entities (including JISD) and the NATO Education and Training Facilities (NETFs) community.
• Demonstrated ability to deliver a Learning Architecture and experience with SFIA and NICE frameworks.
• Strong project management skills.
• The candidate has a NATO SECRET security clearance, provided by the national security organization valid at the time of submission of the bid and covering the period of the contract
• Experience with working in an international environment comprising both military and civilian elements.
• Excellent written and verbal communication skills
• Demonstrable experience of working with NATO International Staff (IS) Human Resources (HR) and NATO International Military Staff (IMS) HR with regards to the mapping of Cybersecurity roles
• Demonstrable experience of NATO Lessons Learned process (for the purpose of quality  ssurance).
• Demonstrable experience with collaboration with NATO Enterprise entities in their implementation of the NATO Enterprise Digital Transformation Action Plan.

Language Proficiency

• Level 3 English language skills according to NATO STANAG 6001: Listening (3); Speaking (2); Reading (3); and Writing (2) or according to Common European Framework of Reference for Language level B2-C1/Upper Intermediate-Advanced level)

See more jobs at EMW, Inc.

Apply for this job

Deadline Date:Wednesday 30 October 2024

Requirement: Project Coherence and Administration

Location: Off site to NCIA Premises, ON SITE MoD Corsham (access to appropriate NATO and UK digital services required, which are not available elsewhere).

Period of Performance:2024 BASE: As soon as possible not later than 25th November 2024 (tentative) – 31st December 2024 with possibility to exercise the following options:

2025 Option: 1st January 2025 until 31st December 2025

2026 Option: 1st January 2026 until 31st December 2026

2027 Option: 1st January 2027 until 31st December 2027

Required Security Clearance: NATO COSMIC TOP SECRET and GBR Developed Vetting (GBR requirement) [See Section 7 below]

Great Britain (GBR) C2 Support & Cooperation Project Coherence and Administration Off-Site Embedded within GBR Ministry of Defence (MOD) Corsham

1 INTRODUCTION

The NATO Information and Communication Agency (NCI Agency) located in The Hague, The Netherlands, is currently involved in the development of joint, new capabilities/services for United Kingdom (GBR) / NCIA / North Atlantic Treaty Organisation (NATO) as well as the support of existing capabilities and services. In the light of these activities, the C2 Centre is looking for an experienced Project coherence administrator.

More specifically, the work will support the NCIA Liaison Officer (LO) on Defence Digital (DD) GBR / NCIA joint ventures and provide a deputy focal point within DD, MOD Corsham for NCIA / NATO activities.

2 OBJECTIVES

The objectives of this statement of work are to:

• Support the development and validation of C2 Services Enabling requirements, architectural products and technical specifications;
• Support the Alliance Federation information sharing concepts, services and specifications. This includes support to NATO interoperability exercises;
• Providing technical support for C2 activities in the area of identity and access management security, Data Management and Message and Information transformation and standardisation.

3 SCOPE OF WORK

Under the direction of the NCIA project manager and the embedded NICA / DD LO, the contractor will deliver the following services using Agile methodology:

• Provide input and update the GBR BI Weekly Project meeting documentation.
• Coordinate UK-NCIA workshops and planning meetings.
• Support the embedded LO in development of current and future capabilities and services.
• Provide ad-hoc project management / leadership duties (where agreed by the LO).
• Provide input to, and coordinate, timetabling / diary activities between themselves and the LO.
• Act as the deputy embedded LO in the absence of the LO.

The coordination will be carried out accessing remotely the NCIA Reach IT system and the GBR MODNET IT system.

The contractor will be part of a team (NCIA project manager, embedded LO, and NCIA Subject Matter Experts (SMEs), etc.) and will work using an Agile and iterative approach using multiple sprints. Each sprint is planned for a duration of one month. The content and scope of each sprint will be agreed with the project manager and the embedded LO during the sprint-planning meeting, in writing.

The collective deliverables comprise a Sprint of one month duration. They are to be peer-reviewed ahead of the final version for each product being delivered. Direction and guidance on the reporting format (verbal brief, written brief, report, design, specification etc) will be provided by the project manager and the LO.

The SPRINT main activists are the following:

1. Author desk level GBR C2 and Cooperation Project Engagement Reports from formal meetings – fortnightly;

2. Author OF5-level GBR C2 and Cooperation Project Engagement Reports – monthly;

3. Follow-up individual actions generated from the engagement reports, providing deliverables in the format specified by the project manager and / or the LO – weekly;

4. Supporting the LO, establish and maintain contact with the GBR Domains (Maritime, Land, Air, Cyber, Space). Record and update risks, issues, assumptions, dependencies and opportunities (RAIDO). Capture and log in the RAIDO log – monthly;

5. Take day-to-day charge of administration for DD (and wider GBR Defence) engagements with NCIA (and where appropriate, wider NATO). Drive and collate activities with stakeholders on the DD-NCIA Engagement Matrix – updated on an ongoing basis;

6. Deputise on a monthly basis for the LO, when he / she is in The Hague or on Temporary Duty (TDY) elsewhere.

7. Produce a Sprint Report summarising the sprint activities for the month. Advise on further RAIDO which the GBR C2 and Cooperation Project needs to consider.

4 PAYMENT MILESTONES

The payment shall be dependent upon successful acceptance of the Delivery Acceptance Sheet (DAS) – (Annex B) including the EBA Receipt number.

Payment will be provided based on these deliveries as indicated in the table

Invoices shall be accompanied with a Delivery Acceptance Sheet (Annex B) signed by the Contractor and project authority.

The following deliverables are expected from this statement of work are described below.

Deliverable: 1 Sprint

Payment Milestones: Upon completion of each sprint and at the end of the work.

2025 OPTION: 01 January 2025 to 31 December 2025

Deliverable: Up to 12 sprints

Payment Milestones: Upon completion of each fourth sprint and at the end of the service. Completion of each milestone shall be accompanied documented in Delivery Acceptance Sheet (DAS) – (Annex B), signed for acceptance by the Purchaser’s authorized point of contact and the Contractor

2026 OPTION: 01 January 2026 to 31 December 2026

Deliverable: Up to 12 sprints

Payment Milestones: Upon completion of each fourth sprint and at the end of the service. Completion of each milestone shall be accompanied documented in Delivery Acceptance Sheet (DAS) – (Annex B), signed for acceptance by the Purchaser’s authorized point of contact and the Contractor

Based on the same deliverable timeframe and cost the NCIA team reserves the right to exercise a number of further sprint options.

5 SCHEDULE

This task order will be active immediately after signing of the contract by both parties.

The BASE period of performance is as soon as possible but not later than 2 Dec 24 and will end no later than 2 Dec 24.

If exercised the option 2025, the period of performance is 1 Jan – 31 Dec 2025.

If exercised the option 2026, the period of performance is 1 Jan – 31 Dec 2026.

6 CONSTRAINTS

All the deliverables provided under this statement of work will be based on NCI Agency templates or agreed with the project point of contact.

All code, scripts, documentation, etc. will be stored under configuration management and/or in the provided NCI Agency tools.

NATO will retain the intellectual property rights for all products developed in relation to this project.

7 SECURITY

The duties of the consultants require a valid NATO CTS security clearance.

The expected classification level of the deliverables is NATO Restricted. However, in some particular circumstances it may be decided that a part of the deliverables and the associated work will be classified as NATO COSMIC TOP SECRET (CTS). (CTS is required in order to meet GBR MOD’s requirement for the contractor to have GBR Developed Vetting.)

NB - GBR Developed Vetting will suffice, which must be in place at contract start.

The execution of duties may require the consultants to access information, as well as CIS systems, classified up to NATO SECRET.

[Section 8 omitted by NATO]

9 PRACTICAL ARRANGEMENTS

Service on the contract will be performed off-site at the consultant’s own office or at MoD Corsham. A computer equipment will be provided at NCI Agency-NL for access during scheduled visits for the duration of this contract. The contractor is responsible for office space and computer equipment at their own facilities.

NB - The majority of the work will be performed at MoD Corsham (access to appropriate NATO and UK digital services required, which are not available elsewhere). Any work outside of MoD Corsham will be with the agreement of the employing Project Lead and / or the Liaison Officer.

Extraordinary travel (Purchaser-Directed Travel) may be required to other NATO or non-NATO locations as necessary so agility must be maintained.

Travel expenses will be reimbursed in accordance with Article 5.5 of AAS+ Framework Contract.

This work must be accomplished by ONE contractor.

10 COORDINATION AND REPORTING

The contractor shall participate remotely in daily status update meetings, sprint planning, sprint retrospectives and other meetings, physically in the office, or in person via electronic means using Conference Call capabilities, according to project manager’s instructions.

For each sprint to be considered as complete and payable, the contractor must report the outcome of his/her work during the sprint, first verbally during the retrospective meeting and then in written within three (3) days after the sprint’s end date. The format of this report shall be a short email to the project manager mentioning briefly the work held and the development achievements during the sprint.

11 QUALIFICATIONS

[See Requirements]

11 QUALIFICATIONS

11.1 THE FOLLOWING EXPERTISE AND KNOWLEDGE IS ESSENTIAL FOR THIS REQUIREMENT:

The consultancy support for this work requires a project coherence and administrator with the following qualifications:

• Knowledge of Defence Digital (DD) Corsham activates (including Commination Information & System (CIS) delivery mechanisms, Support mechanisms, Network compliance) and structure.
• Hold NATO CTS. NB - GBR Developed Vetting is also required (by GBR).
• Experience in working with NATO/NCIA particularly in problem management, assurance of services and Crypto delivery.
• Proven ability to negotiate with Project teams, chair/administrate and participate in Capability Planning meetings.
• Knowledge of Microsoft office productivity tools (Office/Excel/PowerPoint).
• Proven ability to integrate and work in a multinational team.
• Fluent business English and the ability to present when called upon to do so.

See more jobs at EMW, Inc.

Apply for this job

EMW, Inc. is looking for a Power Apps Developer to support our team on Redstone Arsenal in Huntsville, AL. This position requires an active Secret clearance or is eligible to obtain a clearance. This is currently a hybrid role with 2 days onsite, subject to change at any time.

Responsibilities and Qualifications:

The ideal candidate responsible for the further development, implementation, design, and support of the expansion of the Microsoft 365 Power Platform.

• Extensive experience in the Microsoft Power Platform - MS PowerApps, Flow, and Power BI 2
• Expertise in designing and developing custom business apps using Canvas Apps and Model Driven Apps; Portal/Power Pages
• Hands-on experience in Microsoft Dataverse; experience in creating solutions and custom connectors.
• Experience with Office 365 development utilizing PowerApps, Flow, and Power BI, Teams, and SharePoint Online Experience designing solutions.
• Portal/Power Pages
• Work with Product Owner/Business Analysts to understand functional requirements and interact with other cross-functional teams to architect, design, develop, test, and release features.
• Experience with Power Automate Cloud Flows, Desktop Flows, business process Flows, and Process Advisor
• Experience JavaScript, .NET,
• Experience with Software Development Life Cycle Process (may include SDLC, Agile, SCRUM, Lean, etc.)

• Security Clearance: SECRET, Interim SECRET required to begin work.
• Preferred Education and Experience: BA/BS with 3+ years relative experience or AA/AS with 5

See more jobs at EMW, Inc.

Apply for this job